Install any skill in seconds. Free to start, no credit card required.
Get Started Free →penpot/review-code
Code review flow — review a diff, PR, or code change, delegating the review to a subagent that follows the code-review-criteria skill.
Passed 18 of 22 test cases with the skill, and 10 of 22 without it.
and 6 more in the full report
8 fixed10 passed either way4 still failing0 broke1 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Please review the diff between `main` and my working branch `feature/payment-gateway`. I'd like an in-depth assessment of the changes to make sure everything looks good before I submit it for merging.
| Checked | Without skill | With skill |
|---|---|---|
| Delegates the branch review to the general subagent. | Missed | Passed |
| Includes code-review-criteria in the subagent delegation prompt. | Missed | Passed |
The instructions your model reads when the skill loads.
Act as a senior software engineer and perform a thorough code review.
/review-code.general subagent (via the task tool), unless the
user specifies another agent. Include in the prompt the
code-review-criteria skill name and all user context./make-a-plan to make a plan to address
them.This flow is read-only for the duration of the review: from the moment it starts until the user considers the review finished (including any feedback, questions, or clarifications about it). During that period, never fix, implement, edit files or create commits — not even "obvious" fixes derived from the findings. Once the user explicitly states the review is done (or moves on to a different task), this rule no longer applies and you act as a normal build agent again.
test cases passed, vs 10 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.