스킬 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.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

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