Use this skill when conducting or improving code reviews. Provides structured review processes, conventional comments patterns, language-specific checklists, and feedback templates. Ensures consistent, constructive, and thorough code reviews across teams.
SkillScore88Maintained
Automatic
◆Coding packcode-reviewqualitycollaboration
Last verified 9/2/2026
What it changes
Passed 21 of 24 test cases with the skill, and 15 of 24 without it.
Without skill63%
With skill88%
Checks it passed that the model alone missed
Identifies bug as a merge-blocking comment label
Identifies security as a merge-blocking comment label
Identifies breaking as a merge-blocking comment label
and 10 more in the full report
7 fixed14 passed either way2 still failing1 broke
Pass-rate lift
+25 pp
Tokens
+246%
Agent turns
0%
Response time
+7%
Model gemini-3.6-flashMeasured 9/2/2026v121 of 24 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
A reviewer needs to plan their calendar for reviewing PRs today. One PR is 150 lines (small), another is 350 lines (medium), and a third is 700 lines (large). What are the estimated time budgets for reviewing each size?
What was checked, without and with the skill
Checked
Without skill
With skill
Allocates 15 to 30 minutes for reviewing small pull requests
Missed
Passed
Allocates 30 to 60 minutes for reviewing medium pull requests
Missed
Passed
Allocates 1 to 2 hours for reviewing large pull requests
Missed
Passed
case-15 · gemini-3.6-flash · 9/2/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md908 lines3 files
Code Review Playbook
Overview
This skill provides a comprehensive framework for effective code reviews that improve code quality, share knowledge, and foster collaboration. Whether you're a reviewer giving feedback or an author preparing code for review, this playbook ensures reviews are thorough, consistent, and constructive.
When to use this skill:
Reviewing pull requests or merge requests
Preparing code for review (self-review)
Establishing code review standards for teams
Training new developers on review best practices
Resolving disagreements about code quality
Improving review processes and efficiency
Code Review Philosophy
Purpose of Code Reviews
Code reviews serve multiple purposes:
Quality Assurance: Catch bugs, logic errors, and edge cases
Knowledge Sharing: Spread domain knowledge across the team
Consistency: Ensure codebase follows conventions and patterns
Mentorship: Help developers improve their skills
Collective Ownership: Build shared responsibility for code
Documentation: Create discussion history for future reference