Menu
Review a Go package for adherence to project Go guidelines (naming, architecture, structure, workflow). Takes a package path and reports violations.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Implement a feature fully autonomously in the background as a Workflow — decompose, then run each task through test-design → implement → refactor → review → verify, closing on executed evidence instead of human approval gates. Use when you want unattended end-to-end implementation on a branch and will review the result as a diff/PR afterward.
Deliver a large user story as multiple parallel PRs. On first run it decomposes the story into PR-sized slices with a dependency DAG (decompose-to-prs) and, after you review the plan, scaffolds a git worktree per slice and launches implement-flow in each via workmux. Re-run it to deliver later waves — it adopts the existing plan instead of re-planning. Use when a story is too big for one PR.
Implement a feature autonomously through the full test-design → test-write → implement → refactor → review loop, pausing only for plan approval and pre-commit approval.
Implement a feature autonomously through the full test-design → test-write → implement → refactor → review loop, running independent tasks in parallel (isolated git worktrees) and pausing only for plan approval and pre-commit approval.
Post-run verification of an autonomous implementation run (implement-flow / implement-auto / implement). Runs the run-verifier agent to catch the failure modes the evidence gate can't see — staged tails, dead code, vacuous receipts, collapsed commits — and, with --fix, remediates them. Use after an unattended run, before trusting its "done".
Write or edit an article or note. Follows writing style guidelines for clarity and consistency.
| name | review-go |
| description | Review a Go package for adherence to project Go guidelines (naming, architecture, structure, workflow). Takes a package path and reports violations. |
| disable-model-invocation | true |
Review a Go package against project guidelines: $ARGUMENTS
Before reviewing, read ALL guidelines:
cat ~/.config/ai/guidelines/go/naming-patterns.md
cat ~/.config/ai/guidelines/go/architecture-principles.md
cat ~/.config/ai/guidelines/go/development-workflow.md
Resolve $ARGUMENTS to a package path. If it's a relative path, resolve from the current directory. If it's a Go import path, find the corresponding directory.
Find all .go files in the package (including subpackages):
fd -e go . <package-path>
Understand the layout:
For each file, type, interface, and function:
command, event), not technical names (impl, manager, handler_manager, util, helper)command.Bus, not command.CommandBus). No redundant package name in the type name.inmemory.go, esdb.go), not generic (impl.go, default.go, implementation.go)NewX, NewXWithY)var _ Interface = (*impl)(nil) present for each implementationconcept/interface.go + concept/subpackage/implementation.go## Package Review: `<package-path>`
### Structure
[Brief description of the package layout]
### Findings
#### 1. [Category] — [file:line]
**Issue**: [What violates the guidelines]
**Guideline**: [Which guideline and specific rule]
**Fix**: [Concrete action to resolve]
[Repeat for each finding]
### Summary
- **Files reviewed**: [count]
- **Violations found**: [count]
- **Verdict**: [PASS / NEEDS WORK]
[If NEEDS WORK, list the top 3 most impactful fixes in priority order]
/review-go-tests for that)