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.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
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.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "golang-lint". A bodyclose warning reports an unclosed HTTP response body.
Resultado esperado:
Recommendation: fix it. Close the response body on every successful request path because the warning identifies a real connection leak.
Usando "golang-lint". A long table-driven test triggers funlen.
Resultado esperado:
Recommendation: consider a scoped suppression. Name funlen and explain that test length follows the case table.
Usando "golang-lint". A legacy repository has more than two thousand warnings.
Resultado esperado:
Adopt checks for changed code first, group findings by category, apply reviewed fixes, and reduce the existing backlog in measured stages.
Auditoría de seguridad
Riesgo medioAll 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.
Preocupaciones de seguridad confirmadas (1)
Factores de riesgo
⚙️ Comandos externos (40)
📁 Acceso al sistema de archivos (4)
🌐 Acceso a red (1)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/samber-golang-lint/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/samber-golang-lint?utm_source=security_passport_badge)Insignia 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>Tarjeta para insertar
<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>Citas académicas (APA · BibTeX · CFF)
Cita 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/1Cita 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"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
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.
Prueba estos 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.
Mejores prácticas
- 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.
Evitar
- 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.
Preguntas frecuentes
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?
Detalles del desarrollador
Autor
samberLicencia
MIT
Versión del autor
v1.4.1
Revisión de Skillstore
r1
Repositorio
https://github.com/samber/cc-skills-golang/tree/22c58a55a0a799b901aa251172923180bad9e010/skills/golang-lintRef.
e5464e662405de6361fdde6b984f9ea865635f64
Actualidad del mantenimiento
8/9/2026
Uso
1 descargas · 0 vistas
Estructura de archivos