team-code-review
Installation
SKILL.md
Team Code Review
Before each dispatch or retry, read host dispatch and supply its resolved installed paths. Before artifact work, read artifact schema. Before the tier sort, read finding format. Before each consuming step, read its linked shared rules from this installed skill directory. If a required read fails, stop that step with the exact path. Never use checkout fallback or recursive loading. Before finalizing prose you author, read the writing standards. Relay completed reviewer reports unchanged.
Core contracts
- Require
1-task.md, a non-default branch, at least one commit beyond the merge-base, and a tree clean outsidedocs/plans/; in multi-repo mode, every worktree4-repos.mdlists. - Write one
review-<n>.mdper completed round; never overwrite a record. - Never ask the user which Blocking or Major items to address (the no-consult rule). The loop has no count cap; it ends only when no Blocking or Major finding remains.
- At PASS, return to the
/teamphase loop in the same turn when the TodoWrite ledger holds aPRphase item; otherwise print the Next line for/team-security-review. Never loadteam-security-revieworteam-pr.
Procedure references
Read each reference completely when reaching it, in order.