Comprehensive code review checklist for Go projects. Evaluates code quality, idiomatic patterns, error handling, naming, package structure, and test coverage. Use when reviewing Go code, PRs, or before merging changes. Trigger examples: "review this code", "check this PR", "code review", "review Go file". Do NOT use for security-specific audits (use go-security-audit) or performance-specific analysis (use go-performance-review).
EnglishDebug Go failures by reproducing the bug as a focused test, tracing root cause, fixing minimally, and verifying with race-enabled tests. Use when the user mentions a bug, panic, deadlock, race, leak, hang, crash, segfault, regression, flaky test, or any Go failure that needs reproducing — for non-Tier-1 paths only (Tier 1 bugs use go-tdd-bugfix).
EnglishModernize Go code to use current language features and standard library additions. Covers generics, log/slog, errors.Join, slices/maps packages, range-over-func, and iterators introduced in Go 1.21-1.23+. Use when: "modernize", "update to modern Go", "use generics", "replace interface{}", "upgrade Go version", "slog", "errors.Join", "range over func", "iterators". Do NOT use for: general code style (use go-coding-standards), error handling philosophy (use go-error-handling), or logging architecture (use go-observability).
EnglishPre-release Go checklist for services, libraries, and CLIs (tests + race + lint + govulncheck + allowed-modules + TDD ceremony + CHANGELOG + API docs). Use when the user asks to release, ship, deploy, cut a tag, prepare a release, or do a pre-release / pre-deploy check.
EnglishUse this skill for any request to fix a bug, debug a failure, or address a regression in code paths matching .tdd/tdd-config.json tier1pathregexes. Reproduces the bug as a failing test BEFORE diagnosing or fixing. Two human approval gates.
EnglishUse this skill for any request to implement, add, build, or create new functionality in code paths matching .tdd/tdd-config.json tier1pathregexes. Drives spec -> APPROVED SPEC -> failing test -> APPROVED GREEN -> implementation -> APPROVED IMPLEMENTATION -> commit -> refactor, with three human approval gates.
EnglishReview a database migration (SQL, golang-migrate, goose, Flyway, etc.) for safety, reversibility, zero-downtime correctness. DB safety review is high-stakes; only invoke explicitly when reviewing a migration.
EnglishPlan and implement the smallest safe Go change with red-before-green where tractable. Use for any routine Go change to non-Tier-1 paths — small features, bug fixes, refactors, lint cleanups, dependency bumps, or any change where the user says "implement", "add", "fix", "update", "change", or "refactor" and the touched paths are NOT covered by .tdd/tdd-config.json tier1pathregexes.
EnglishPost-implementation cleanup pass that explicitly looks for code to delete, inline, or reuse rather than add. Use after any implementation finishes and tests pass — before opening a PR — to remove AI-generated bloat, single-use abstractions, speculative config, dead exports, and tests that mirror implementation. Trigger when the user says "clean up", "simplify", "shrink the diff", "reduce bloat", "prepare PR", or whenever a PR exceeds ~200 lines.
EnglishScaffold a new Go service, package, or subsystem following the existing repo conventions (matches existing structure, names, entry points, test layouts). Use when the user asks to scaffold, create, or set up a new package / module / service / binary / worker / handler.
EnglishCodex deep ops-safety review of a proposed Bash command BEFORE it executes. Invoke MANUALLY (via /ops-preflight) when the ops-risk-triage hook has emitted an ask for an inframutation, externalread, destructive, or unknown command and you want a second opinion on blast radius / rollback / required post-checks before approving. NOT for code review (use go-code-review). NOT auto-invoked.
EnglishTurn an escaped defect or production incident into a concrete prevention patch plan (root cause + control gap + multi-layer fix). Declaring an incident is intentional; only invoke explicitly when the operator says this is post-incident or postmortem work.
English
AGENT SKILLS ATLASIncludes Go Code Review, Go Modernize, Go Release Check, and other workflows.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Go Code Review
Comprehensive code review checklist for Go projects. Evaluates code quality, idiomatic patterns, error handling, naming, package structure, and test coverage. Use when reviewing Go code, PRs, or before merging changes. Trigger examples: "review this code", "check this PR", "code review", "review Go file". Do NOT use for security-specific audits (use go-security-audit) or performance-specific analysis (use go-performance-review).
Go Debug
Debug Go failures by reproducing the bug as a focused test, tracing root cause, fixing minimally, and verifying with race-enabled tests. Use when the user mentions a bug, panic, deadlock, race, leak, hang, crash, segfault, regression, flaky test, or any Go failure that needs reproducing — for non-Tier-1 paths only (Tier 1 bugs use go-tdd-bugfix).
Go Modernize
Modernize Go code to use current language features and standard library additions. Covers generics, log/slog, errors.Join, slices/maps packages, range-over-func, and iterators introduced in Go 1.21-1.23+. Use when: "modernize", "update to modern Go", "use generics", "replace interface{}", "upgrade Go version", "slog", "errors.Join", "range over func", "iterators". Do NOT use for: general code style (use go-coding-standards), error handling philosophy (use go-error-handling), or logging architecture (use go-observability).
Go Release Check
Pre-release Go checklist for services, libraries, and CLIs (tests + race + lint + govulncheck + allowed-modules + TDD ceremony + CHANGELOG + API docs). Use when the user asks to release, ship, deploy, cut a tag, prepare a release, or do a pre-release / pre-deploy check.
Go TDD Bugfix
Use this skill for any request to fix a bug, debug a failure, or address a regression in code paths matching .tdd/tdd-config.json tier1pathregexes. Reproduces the bug as a failing test BEFORE diagnosing or fixing. Two human approval gates.
Go TDD Feature
Use this skill for any request to implement, add, build, or create new functionality in code paths matching .tdd/tdd-config.json tier1pathregexes. Drives spec -> APPROVED SPEC -> failing test -> APPROVED GREEN -> implementation -> APPROVED IMPLEMENTATION -> commit -> refactor, with three human approval gates.
Migration Review
Review a database migration (SQL, golang-migrate, goose, Flyway, etc.) for safety, reversibility, zero-downtime correctness. DB safety review is high-stakes; only invoke explicitly when reviewing a migration.
Minimal Go Change
Plan and implement the smallest safe Go change with red-before-green where tractable. Use for any routine Go change to non-Tier-1 paths — small features, bug fixes, refactors, lint cleanups, dependency bumps, or any change where the user says "implement", "add", "fix", "update", "change", or "refactor" and the touched paths are NOT covered by .tdd/tdd-config.json tier1pathregexes.
Negative Diff
Post-implementation cleanup pass that explicitly looks for code to delete, inline, or reuse rather than add. Use after any implementation finishes and tests pass — before opening a PR — to remove AI-generated bloat, single-use abstractions, speculative config, dead exports, and tests that mirror implementation. Trigger when the user says "clean up", "simplify", "shrink the diff", "reduce bloat", "prepare PR", or whenever a PR exceeds ~200 lines.
New Module Scaffold
Scaffold a new Go service, package, or subsystem following the existing repo conventions (matches existing structure, names, entry points, test layouts). Use when the user asks to scaffold, create, or set up a new package / module / service / binary / worker / handler.
Ops Preflight
Codex deep ops-safety review of a proposed Bash command BEFORE it executes. Invoke MANUALLY (via /ops-preflight) when the ops-risk-triage hook has emitted an ask for an inframutation, externalread, destructive, or unknown command and you want a second opinion on blast radius / rollback / required post-checks before approving. NOT for code review (use go-code-review). NOT auto-invoked.
Postmortem Fix
Turn an escaped defect or production incident into a concrete prevention patch plan (root cause + control gap + multi-layer fix). Declaring an incident is intentional; only invoke explicitly when the operator says this is post-incident or postmortem work.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Go Code Review skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: Apache-2.0. The author’s terms apply.