From tech-lead
This skill should be used when the user asks for "code review", "review my changes", "review this PR", "check my code", "pre-merge review", "review diff", or mentions reviewing code quality, implementation correctness, or preparing changes for merge.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tech-lead:code-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill should be used when the user asks for "code review", "review my changes", "review this PR", "check my code", "pre-merge review", "review diff", or mentions reviewing code quality, implementation correctness, or preparing changes for merge.
This skill should be used when the user asks for "code review", "review my changes", "review this PR", "check my code", "pre-merge review", "review diff", or mentions reviewing code quality, implementation correctness, or preparing changes for merge.
Code review following the Review Pyramid methodology — a prioritized approach that focuses on what matters most.
▲
/|\ 5. Code Style (Nit) ← Least important, automatable
/ | \
/ | \ 4. Tests
/ | \
/ | \ 3. Documentation
/ | \
/ | \ 2. Implementation Semantics ← High priority
/ | \
/________|________\ 1. API Semantics ← Most critical, review first
Key insight: Review from bottom to top. API and implementation issues are far more important than style issues.
Fast first pass using quick-reviewer agent (sonnet):
Thorough analysis using code-reviewer agent (opus):
| Trigger | Action |
|---|---|
| "Review my staged changes" | /review:diff staged |
| "Review before I merge" | /review:diff main --mode=full |
| "Quick check my code" | /review:diff --mode=quick |
| "Deep review this feature" | /review:diff main --task="..." --mode=deep |
--task flag for accurate business logic reviewpyramid.md — Detailed explanation of the Review Pyramidapi-semantics.md — API review checklistimplementation.md — Implementation review checklistsecurity.md — Security review checklisttesting.md — Test review checklistnpx claudepluginhub ruslan-korneev/claude-plugins --plugin tech-leadCode review with semantic diffs, expert routing by file type, and auto-task creation for critical issues. Works on staged changes, files, or PRs.
Systematically evaluates pull requests for correctness, design, readability, and tests, delivering actionable and kind feedback based on Google's engineering practices.
Reviews diffs and pull requests with constructive feedback, systematic analysis, and collaborative improvement. Establishes review standards and mentors teams.