Skills Guide

Go Code Auditor

VerifiedSafe

Audits Go codebases for common anti-patterns and risks including unchecked errors, goroutine leaks, interface bloat, and package hygiene issues. It runs static analysis with go vet, scans for error discarding patterns, reviews goroutine safety, and checks interface design and package structure. Ideal for identifying code quality issues and potential runtime bugs before they occur.

Download and use
Sby Skills Guide Bot
DevelopmentAdvanced
6/2/2026
Claude Code
#go#audit#static-analysis#error-handling#goroutine-leaks

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

Systematically scans a Go codebase for common anti-patterns such as unchecked errors, goroutine leaks, interface bloat, and package hygiene issues.

Strengths

  • Leverages go vet and static analysis tools for thorough coverage
  • Produces a structured report with file:line references
  • Catches subtle issues like discarded errors and unmanaged goroutines

Limitations

  • May generate false positives that require manual verification
  • Does not catch runtime errors or non-goroutine concurrency issues
  • Depends on the quality of grep patterns and AI inference
When to use it

Best used before code review, merge, or release to improve Go code quality.

When not to use it

Not suitable for quick checks or when the code is still in flux, as false positives may slow down development.

Security analysis

Safe
Quality score87/100

The skill instructs running 'go vet ./...' (a static analysis tool) and use of grep/read/glob to scan code for anti-patterns. None of these operations are destructive or exfiltrative, and the scope is limited to auditing the local codebase. No risky commands like curl, rm, or token exfiltration are instructed.

No concerns found

How this analysis is made

Examples

Full codebase audit
Audit the Go codebase in the current directory for common anti-patterns.
Targeted audit on specific packages
Run go-audit on the ./cmd and ./pkg directories, focusing on error handling and goroutine safety.
Audit with risk summary
Perform a complete Go audit on this project and provide a risk summary with actionable items.

name: go-audit description: Audit Go codebase for unchecked errors, goroutine leaks, interface bloat, and anti-patterns user-invocable: true allowed-tools: Read, Grep, Glob, Bash

You are a Go code auditor. Systematically scan the codebase for common Go anti-patterns and risks.

Steps

  1. Run static analysis: Execute go vet ./... and report any findings.

  2. Audit error handling:

    • Grep for patterns that discard errors: lines matching = .+\( where the error return is ignored
    • Grep for _ = patterns that might hide error discards
    • Grep for errors.New without %w wrapping in fmt.Errorf at call sites
    • Read flagged files and verify whether errors are properly checked and wrapped

  3. Audit goroutine patterns:

    • Grep for go func and go to find all goroutine launches
    • For each, verify: Is there a way to signal shutdown? Is context passed? Is there error propagation?
    • Check for sync.WaitGroup or errgroup.Group usage around goroutine launches

  4. Audit interface design:

    • Grep for type .+ interface to find all interfaces
    • For each interface, count methods. Flag interfaces with more than 3 methods.
    • Check if each interface has multiple implementations (Grep for the method signatures)
    • Flag interfaces defined in the same package as their only implementation

  5. Audit package hygiene:

    • Check for utils, common, helpers, misc package names
    • Look for circular imports by examining import statements across packages
    • Check for package-level var that introduces global mutable state

  6. Output the audit:

## Audit Report

### Error Handling
[Findings with file:line references]

### Goroutine Safety
[Findings with file:line references]

### Interface Design
[Findings with file:line references]

### Package Hygiene
[Findings with file:line references]

### Risk Summary
[High/Medium/Low risk areas with recommended action items]

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/go-code-auditor-mm5t8av1/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/go-code-auditor-mm5t8av1' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/go-code-auditor-mm5t8av1/download' --output '.skill-downloads/go-code-auditor-mm5t8av1/SKILL.md.part' && mv '.skill-downloads/go-code-auditor-mm5t8av1/SKILL.md.part' '.skill-downloads/go-code-auditor-mm5t8av1/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Grep, Glob, Bash

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/go-code-auditor-mm5t8av1/SKILL.md' && test -s '.skill-downloads/go-code-auditor-mm5t8av1/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/go-audit' && cp -R '.skill-downloads/go-code-auditor-mm5t8av1' '.claude/skills/go-audit'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/go-code-auditor-mm5t8av1'

openskills read 'go-code-auditor-mm5t8av1'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/go-code-auditor-mm5t8av1/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot