Skills golang-lint

📦

golang-lint

Name: golang-lint
Author: samber

v1.4.1 Content revision r1 Medium Risk ⚙️ External commands📁 Filesystem access🌐 Network access

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.

Supports: Codex Code(CC)

📊 72 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

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.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/samber-golang-lint.md Signed manifest GET /api/skills/samber-golang-lint/manifest Signed lockfile GET /api/skills/samber-golang-lint/lockfile

Test it

Using "golang-lint". A bodyclose warning reports an unclosed HTTP response body.

Expected outcome:

Recommendation: fix it. Close the response body on every successful request path because the warning identifies a real connection leak.

Using "golang-lint". A long table-driven test triggers funlen.

Expected outcome:

Recommendation: consider a scoped suppression. Name funlen and explain that test length follows the case table.

Using "golang-lint". A legacy repository has more than two thousand warnings.

Expected outcome:

Adopt checks for changed code first, group findings by category, apply reviewed fixes, and reduce the existing backlog in measured stages.

Security Audit

Medium Risk

v1 • 9/6/2026 Open versioned report

All 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.

Files scanned

814

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Medium

SKILL.md:39

Unpinned Executable Installation

The installation command uses the moving latest version, so later runs can fetch and install different upstream code without review.

SKILL.md line 39 explicitly recommends go install with @latest. Pinning a reviewed version would reduce dependency substitution and reproducibility risk.

Risk Factors

⚙️ External commands (40)

📁 Filesystem access (4)

references/linter-reference.md:46 references/linter-reference.md:46 SKILL.md:47 SKILL.md:73

🌐 Network access (1)

SKILL.md:12

Audited by: codex

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/samber-golang-lint/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/samber-golang-lint/security.svg)](https://skillstore.io/skills/samber-golang-lint?utm_source=security_passport_badge)

HTML badge

<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>

Embed card

<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>

Academic citations (APA · BibTeX · CFF)

APA citation

samber. (2026). golang-lint security audit report (audit version 1) [Author version 1.4.1]. Skillstore. https://skillstore.io/skills/samber-golang-lint/audits/1

BibTeX citation

@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"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

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.

Try These Prompts

Explain One Warning

Explain this golangci-lint warning: [warning]. Tell me what it means and whether I should fix or suppress it.

Create a Lint Configuration

Create a golangci-lint v2 configuration for [project type]. Prioritize correctness and security, set practical thresholds, and explain each choice.

Review Suppressions

Review the nolint directives in my Go changes. Identify unsafe suppressions and propose specific directives with clear justifications.

Plan Legacy Cleanup

Design an incremental lint adoption plan for [repository details]. Group independent work, protect new code, and define verification steps.

Best Practices

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.

Avoid

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.

Frequently Asked Questions

Which golangci-lint version does this skill target?

The included configuration targets golangci-lint v2 and uses its version 2 configuration structure.

Can this skill run linters?

Yes. It can guide or run golangci-lint when the tool is installed and command access is available.

Does it create CI workflows?

No. It focuses on linting configuration and local workflows, then refers CI pipeline work to a separate skill.

When should I use nolint?

Use it only after confirming an intentional pattern or false positive. Always name the linter and explain the reason.

Can it help with legacy repositories?

Yes. It recommends checking changed code first and organizing independent warning categories for staged cleanup.

Does automatic fixing remove every warning?

No. Automatic fixes address supported findings only. Review every change and resolve remaining warnings manually.

Developer Details

Author

samber

License

MIT

Author version

v1.4.1

Skillstore revision

Repository

https://github.com/samber/cc-skills-golang/tree/22c58a55a0a799b901aa251172923180bad9e010/skills/golang-lint

Ref

e5464e662405de6361fdde6b984f9ea865635f64

Maintenance freshness

9/8/2026

Usage

0 downloads · 0 views

File structure

📁 assets/

📄 .golangci.yml

📁 evals/

📄 evals.json

📁 references/

📄 linter-reference.md

📄 nolint-directives.md

📄 SKILL.md