Requesting Code Review
jnmetacode/superpowers-zhCode review helps you catch problems before they grow. You send your work to a reviewer who gets a clean summary, not your messy history. This keeps the focus on what you built, not how you built it.
You should review early and often. Always review after finishing a task, after a big feature, or before merging to main. It is also useful when you are stuck, before refactoring, or after fixing a hard bug.
To start, get the git commit IDs. Then send a code review request with a short description, the expected behavior, and the commit range. Fix critical issues right away. Fix important ones before moving on. Log minor issues for later. If the reviewer is wrong, explain with technical facts.
Add Requesting Code Review skill to your workflow
Global
mkdir -p ~/.claude/skills/requesting-code-reviewProject
mkdir -p .claude/skills/requesting-code-reviewSource Repository
More Code Review & Quality Claude Code Skills
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective