golang-lint
Strengthen Go Projects with golangci-lint
Go teams often struggle to choose linters, understand warnings, and manage legacy backlogs. This skill provides practical golangci-lint configuration, triage, suppression, and cleanup guidance.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "golang-lint" from https://skillstore.io/skills/samber-golang-lint.md and its manifest at https://skillstore.io/api/skills/samber-golang-lint/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « golang-lint ». A bodyclose warning reports an unclosed HTTP response body.
RĂ©sultat attendu:
Recommendation: fix it. Close the response body on every successful request path because the warning identifies a real connection leak.
Utilisation de « golang-lint ». A long table-driven test triggers funlen.
RĂ©sultat attendu:
Recommendation: consider a scoped suppression. Name funlen and explain that test length follows the case table.
Utilisation de « golang-lint ». A legacy repository has more than two thousand warnings.
RĂ©sultat attendu:
Adopt checks for changed code first, group findings by category, apply reviewed fixes, and reduce the existing backlog in measured stages.
Audit de sécurité
Risque moyenAll 55 static alerts are false positives caused by Markdown, comments, standard configuration paths, defensive security terminology, or repository metadata. One medium-risk semantic issue remains: the installation guidance fetches an unpinned latest executable.
Préoccupations de sécurité confirmées (1)
Facteurs de risque
âïž Commandes externes (40)
đ AccĂšs au systĂšme de fichiers (4)
đ AccĂšs rĂ©seau (1)
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/samber-golang-lint/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/samber-golang-lint?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/samber-golang-lint?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-lint/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/samber-golang-lint.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citations académiques (APA · BibTeX · CFF)
Citation APA
samber. (2026). golang-lint security audit report (audit version 1) [Author version 1.4.1]. Skillstore. https://skillstore.io/skills/samber-golang-lint/audits/1Citation BibTeX
@techreport{samber-samber-golang-lint-2026,
author = {samber},
title = {golang-lint security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/samber-golang-lint/audits/1},
note = {Author version 1.4.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-lint security audit report (audit version 1)"
version: "1.4.1"
type: report
authors:
- name: "samber"
date-released: "2026-09-06"
url: "https://skillstore.io/skills/samber-golang-lint/audits/1"
identifiers:
- type: other
value: "skillstore:samber-golang-lint:audit:1"
description: "Skillstore immutable audit report identifier"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Configure a New Project
Create a balanced golangci-lint v2 configuration with practical defaults and documented exclusions.
Triage Existing Warnings
Classify lint findings, fix defects, and add justified suppressions only for verified false positives.
Adopt Linting Incrementally
Plan staged cleanup that protects new code while reducing a large legacy warning backlog.
Essayez ces prompts
Explain this golangci-lint warning: [warning]. Tell me what it means and whether I should fix or suppress it.
Create a golangci-lint v2 configuration for [project type]. Prioritize correctness and security, set practical thresholds, and explain each choice.
Review the nolint directives in my Go changes. Identify unsafe suppressions and propose specific directives with clear justifications.
Design an incremental lint adoption plan for [repository details]. Group independent work, protect new code, and define verification steps.
Bonnes pratiques
- Run lint checks after significant changes and before merging.
- Fix root causes before adding scoped suppressions with explanations.
- Pin the golangci-lint version and review all automatic changes.
Ăviter
- Do not use bare nolint directives without a linter name and reason.
- Do not suppress security or resource findings without strong evidence.
- Do not apply automatic fixes across a repository without reviewing the diff.
Foire aux questions
Which golangci-lint version does this skill target?
Can this skill run linters?
Does it create CI workflows?
When should I use nolint?
Can it help with legacy repositories?
Does automatic fixing remove every warning?
Détails du développeur
Auteur
samberLicence
MIT
Version de lâauteur
v1.4.1
RĂ©vision Skillstore
r1
RĂ©f
e5464e662405de6361fdde6b984f9ea865635f64
RĂ©cence de maintenance
08/09/2026
Utilisation
1 téléchargements · 0 vues
Structure de fichiers
đ assets/
đ .golangci.yml
đ evals/
đ evals.json
đ references/
đ linter-reference.md
đ nolint-directives.md
đ SKILL.md