From david-skills
Audits a Go codebase for production readiness against the book *Production Go*. Covers modules, error handling, concurrency, tests, security, CI/CD, and observability with severity-ranked findings.
How this skill is triggered — by the user, by Claude, or both
Slash command
/david-skills:go-production-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to evaluate a Go codebase against production-focused practices distilled from *Production Go*. Treat the book-derived guidance as intent-level criteria: accept modern equivalents that satisfy the same reliability, correctness, security, and operability goals.
Use this skill to evaluate a Go codebase against production-focused practices distilled from Production Go. Treat the book-derived guidance as intent-level criteria: accept modern equivalents that satisfy the same reliability, correctness, security, and operability goals.
Do not reproduce long passages from the book. Produce an audit, checklist, remediation plan, or code review grounded in repository evidence.
references/production-go-checklist.md before scoring. Use the PG-xx IDs in findings.bash scripts/collect_go_production_signals.sh /path/to/repo > go-production-signals.md
For deeper checks when the environment can support them:
RUN_RACE=1 RUN_BENCH=1 bash scripts/collect_go_production_signals.sh /path/to/repo > go-production-signals.md
pass, partial, fail, unknown, or not applicable.p0, p1, p2, or p3 using the checklist severity guidance.references/audit-report-template.md, matching the user's language.Always prefer evidence from the user's repository over generic advice.
For each finding, include:
PG-39Mark a result as unknown when evidence is unavailable. Do not invent CI, deployment, alerting, or observability details.
Cover these areas unless they are clearly out of scope:
-s, goimports, variable naming, declaration style, exported API shape, and godoc commentsuint, nil maps, map iteration order, JSON tags, exported fields, interface nils, empty interfacesstrings.EqualFold, unicode, and x/textWaitGroup, errgroup, channel balance, handler-spawned goroutines, pollers, map races, locks, atomics, race detectorhttptest, mocks via narrow interfaces, coverage, examples, fuzzingb.N, b.ResetTimer, -benchmem, escape analysis, benchmark comparison disciplinego vet, staticcheck or equivalent, golangci-lint, errcheck, Go Report Card-style checks, documentation/navigation toolingSome tooling names and commands from the source book may have modern replacements. Score the underlying practice, not the exact historical tool, unless the user explicitly asks for a book-literal audit.
Examples:
Lead with the production-readiness verdict. Then provide the scorecard and findings.
Keep generic education short. Most space should go to repository-specific evidence and fixes.
For codebase audits, end with prioritized next actions, not a broad summary.
npx claudepluginhub thedavidweng/skillsReviews Go code against style guide, focusing on critical bugs, race conditions, and maintainability issues. Use for PRs, feature branches, or completed work reviews.
Applies Go best practices for performance, modern syntax, generics, patterns, testing, error handling, and concurrency when writing or reviewing Go code.
Reviews Go code for idiomatic patterns, error handling, concurrency safety, and common mistakes. Useful for .go files, goroutines, interfaces, generics (1.18+), and errors.Join/slog (1.20+/1.21+).