Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →josstei/code-review
Standalone code review methodology for structured, severity-classified code assessment
Passed 15 of 19 test cases with the skill, and 11 of 19 without it.
and 2 more in the full report
5 fixed12 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have modified several files in my working tree. Some changes are staged in git index while others are in previous commits. What exact command should be checked first when determining diff context if no file paths were provided?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies git diff --staged as the primary check when no user paths are provided | Missed | Passed |
The instructions your model reads when the skill loads.
Activate this skill when performing standalone code reviews via the runtime-specific Maestro review entrypoint or during orchestration quality gates (post-phase checks and final completion gate). This skill provides the methodology for scoping, executing, and reporting code reviews.
Determine review scope using the following priority order:
glob tool to resolve them to concrete file paths before delegating to the code-reviewer agentgit diff --staged produces output, review staged changesgit diff HEAD~1Always confirm the detected scope with the user before proceeding.
If scope is provided as file paths and a git diff is empty for some paths (for example, new unstaged files), include those files' current contents directly in review context so they are still reviewed.
code-reviewer agent with:
When delegating to the code-reviewer agent, include:
test cases passed, vs 11 / 19 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.