Requesting Code Review
Sends a reviewer subagent the diff and the requirements, not the session history.
Install
/plugin install superpowers@claude-plugins-official
Called after a task or a sizable feature is finished and before a merge, to bring in a reviewer that never saw the session.
- Author
- Jesse Vincent (obra)
- License
- MIT
The base and head commits are collected first, then a reviewer agent receives a package built around the change itself: what was asked for, what the diff contains, and where the boundaries sit. Leaving the session's reasoning out of that package is deliberate — the reviewer judges the work product instead of agreeing with how it was reached. Findings come back triaged by severity, and answering one with a technical argument is a legitimate outcome.
Similar skills
Code Review Excellence
SkillTurns pull request review into a repeatable checklist instead of taste.
Receiving Code Review
SkillRequires understanding and checking review feedback before acting on any of it.
Code Simplifier
SkillRefines recently modified code for clarity and consistency without changing behaviour.
Comments(0)
Sign in to comment