Receiving code review
Consult after receiving review feedback and before implementation when the feedback needs evidence-based evaluation.From its SKILL.md
npx -y skills add BB-84C/superpowers-lite --skill receiving-code-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.8 KB, as published. Nobody here has run it
Receiving Code Review
Read feedback and verify it against code, requirements, and current behavior. Treat review comments as evidence to evaluate, not orders or a social exchange.
Clarify ambiguity only when it changes intent, coupling, or safety. Independent and clear items may proceed while a separate load-bearing question is resolved; do not turn unrelated fixes into a one-item ritual. For accepted findings, state the observed issue, chosen change, and validation.
Push back when evidence shows a conflict with contracts, compatibility, architecture, or real usage. Keep the response factual; gratitude style is not a workflow requirement.