技能 golang-lint

📦

golang-lint

Name: golang-lint
Author: samber

v1.4.1 內容修訂 r1 中風險 ⚙️ 外部命令📁 檔案系統存取🌐 網路存取

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.

支援: Codex Code(CC)

📊 72 尚可

Maintain this Skill? Claim it 📊 72 尚可

使用我的智慧代理安裝

將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。

智能體請求

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.

你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。

Agent 可讀資源

當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。

Markdown 詳情 GET /skills/samber-golang-lint.md 已簽名 manifest GET /api/skills/samber-golang-lint/manifest 已簽名 lockfile GET /api/skills/samber-golang-lint/lockfile

測試它

正在使用「golang-lint」。 A bodyclose warning reports an unclosed HTTP response body.

預期結果:

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

正在使用「golang-lint」。 A long table-driven test triggers funlen.

預期結果:

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

正在使用「golang-lint」。 A legacy repository has more than two thousand warnings.

預期結果:

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

安全審計

中風險

v1 • 2026/9/6 開啟版本化報告

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.

已掃描檔案

814

分析行數

複核項目

已忽略的誤報

已確認的安全問題 (1)

中

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.

風險因素

⚙️ 外部命令 (40)

📁 檔案系統存取 (4)

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

🌐 網路存取 (1)

SKILL.md:12

審計單位: codex

分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。

開啟版本化報告

複製報告連結

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

Markdown 徽章

[![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 徽章

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

嵌入卡片

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

學術引用 (APA · BibTeX · CFF)

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

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"

Skillstore 評分

評分依據證據置信度: 中

架構

100

可維護性

內容

社群

規範符合度

你可以打造什麼

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.

試試這些提示

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.

最佳實務

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.

避免

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.

常見問題

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.

開發者詳細資訊

作者

samber

授權

MIT

作者版本

v1.4.1

Skillstore 修訂

儲存庫

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

引用

e5464e662405de6361fdde6b984f9ea865635f64

維護新鮮度

2026/9/8

使用量

1 次下載 · 0 次瀏覽

檔案結構

📁 assets/

📄 .golangci.yml

📁 evals/

📄 evals.json

📁 references/

📄 linter-reference.md

📄 nolint-directives.md

📄 SKILL.md