Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale.
SkillScore73Maintained
Automatic
◆Coding pack
Last verified 8/13/2026
What it changes
Passed 16 of 22 test cases with the skill, and 3 of 22 without it.
Without skill14%
With skill73%
Checks it passed that the model alone missed
Stage 2 is Correctness.
Stage 5 is Security & Performance.
Stage 1 is Requirements Compliance.
and 18 more in the full report
14 fixed2 passed either way5 still failing1 broke
Pass-rate lift
+59 pp
Tokens
+19%
Agent turns
0%
Response time
-38%
Model gemini-3.6-flashMeasured 8/13/2026v116 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
When filling out the markdown Review Checklist Summary for a pull request review, what verdict options must appear at the bottom?
What was checked, without and with the skill
Checked
Without skill
With skill
The verdict line lists '[ ] Approve [ ] Request Changes [ ] Comment'.
Missed
Passed
case-12 · gemini-3.6-flash · 8/13/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md155 linessingle file
Structured Code Review
You are performing a structured, multi-stage code review. This methodology ensures thorough review while providing actionable, constructive feedback.
Core Principle
Review in stages. Each stage has a specific focus. Don't mix concerns.
A structured review catches more issues and provides better feedback than an unstructured scan.
Review Stages
Stage 1: Requirements Compliance
First, verify the code meets its requirements.
Checklist:
Implements stated requirements
Handles specified edge cases
No scope creep (unexpected additions)
No missing functionality
Feedback at this stage:
"This doesn't appear to handle the case when X is empty"
"The requirement specified Y, but this implements Z"
"This adds feature F which wasn't requested - is that intentional?"
Stage 2: Correctness
Next, verify the code works correctly.
Checklist:
Logic is sound
No obvious bugs
Error paths are handled
No unfinished code (TODOs without tickets)
Feedback at this stage:
"This will throw if user is null"
"The loop exits early before processing all items"
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end tests; structuring test cases or test suites; applying TDD or BDD practices; working with mocks, stubs, spies, or fakes; improving test coverage or reducing flakiness; or needs guidance