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.
使用我的智能体安装
将此请求复制给你的智能体,其中包含权威 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、爬虫或脚本需要干净上下文,而不是读取完整页面时,请使用这些链接。
测试它
正在使用“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.
安全审计
中风险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.
已确认安全问题 (1)
风险因素
⚙️ 外部命令 (40)
📁 文件系统访问 (4)
🌐 网络访问 (1)
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据,不判断该 Skill 是否安全。
复制报告链接
https://skillstore.io/skills/samber-golang-lint/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](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/1BibTeX 引用
@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 评分
评分依据 证据置信度: 中你能构建什么
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 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.
最佳实践
- 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?
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?
开发者详情
作者
samber许可证
MIT
作者版本
v1.4.1
Skillstore 修订
r1
引用
e5464e662405de6361fdde6b984f9ea865635f64
维护新鲜度
2026/9/8
使用量
1 次下载 · 0 次浏览
文件结构