requesting-code-review
Requires completed work to pass through a review pass against requirements before merging or declaring done.
Anatomy
| Parent repo | obra/superpowers |
|---|---|
| Path | skills/requesting-code-review |
| Trigger conditions | "Use when completing tasks, implementing major features, or before merging" |
| Instruction format | yaml-frontmatter-md |
| Required tools | subagents, git |
| Reusability | universal |
| Complexity | medium |
| Ships scripts / examples / tests / boundaries | no / yes / no / yes |
Failure modes
Review quality depends on the reviewer's context separation; a reviewer sharing the producer's session inherits its blind spots.
Verdict
The reviewer-loop pattern packaged as process. Pairs with receiving-code-review to close the loop on both sides.
Related skills
Blocks the agent from claiming work is complete, fixed, or passing until it has run verification commands and confirmed output. Evidence…
Forces root-cause investigation before any fix: reproduce, hypothesize one cause at a time, test the hypothesis, then patch. Bans…
Frequently asked questions
What does the requesting-code-review skill do?
Requires completed work to pass through a review pass against requirements before merging or declaring done.
When does requesting-code-review trigger?
Its stated trigger: "Use when completing tasks, implementing major features, or before merging". Trigger precision is a scored reliability dimension.