Menu
Reviews a spec against the feature description for completeness. Returns PASS or FAIL. Invoked by spec-writer, not directly.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Orchestrates standalone or caller-batched bug fixes via implementor and reviewer subagents using TDD. Handles bugs and verified review findings sequentially, tracks them in a dated checklist, and commits each fix without disrupting a surrounding PR-resolution batch.
Resolve GitHub PR review comments from humans and Copilot, including reviews already auto-requested or in progress. Use for verified comment resolution, sequential bugfix batching, one-push CI/Copilot cycles, and SHA-aware waits that avoid stale-event loops.
Shared conventions for Go projects. Copyright boilerplate, code quality, GoConvey testing, architecture, and commands. Referenced by go-implementor, go-reviewer, and workflow skills.
Go TDD implementation workflow. References implementation-principles, go-conventions, testing-principles, and agent-conduct.
Review Go implementations against spec acceptance tests. References implementation-principles, go-conventions, testing-principles, and agent-conduct.
Shared cross-language delivery workflow and guidance for implementing the simplest sufficient solution, maximizing reuse of existing code, and avoiding speculative abstractions, dependencies, and refactors. Use when implementing or reviewing code in any language.
| name | spec-reviewer |
| description | Reviews a spec against the feature description for completeness. Returns PASS or FAIL. Invoked by spec-writer, not directly. |
| context | fork |
Read and follow agent-conduct before starting.
You have clean context. Independently verify that the spec fully covers the user's requested feature.
For every requirement in the feature description:
Verify alignment with the conventions skill: business logic separated from entry points, external deps mockable, existing code reused, proper file organisation.
