receiving-code-review
Governs how feedback gets handled: technical verification of each finding before implementation, no performative agreement, pushback with evidence where feedback is wrong.
Anatomy
| Parent repo | obra/superpowers |
|---|---|
| Path | skills/receiving-code-review |
| Trigger conditions | "Use when receiving code review feedback, before implementing suggestions" |
| Instruction format | yaml-frontmatter-md |
| Required tools | shell |
| Reusability | universal |
| Complexity | low |
| Ships scripts / examples / tests / boundaries | no / yes / no / yes |
Failure modes
Calibrating disagreement is genuinely hard; over-tuned pushback can turn review resolution into debate.
Verdict
The rarest process skill in the wild: most teams script giving feedback, almost none script receiving it. Agents' sycophancy bias makes this one disproportionately valuable.
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 receiving-code-review skill do?
Governs how feedback gets handled: technical verification of each finding before implementation, no performative agreement, pushback with evidence where feedback is wrong.
When does receiving-code-review trigger?
Its stated trigger: "Use when receiving code review feedback, before implementing suggestions". Trigger precision is a scored reliability dimension.