A second set of eyes catches things you stopped seeing hours ago. Claude Code ships with a /review command that gives you that pass on demand, right from your terminal.
Run the review
Inside a session, run /review (its alias is /code-review). Claude looks at the changes and reports back on correctness, edge cases, and clarity.
claude
> /review
Because it works from your local checkout, you can review a branch before you even open a pull request. Check out the branch, start a session, and ask.
Point it at the right diff
Be specific about what you want looked at. A prompt that names the concern gets a sharper answer than a blanket "review this."
claude "Review the changes on this branch against main. Focus on error handling and any missing input validation."
You can mention files directly with @path so Claude reads them first, which helps when the interesting logic sits in one or two spots.
Security-focused passes
When the change touches auth, user input, or anything network-facing, run /security-review for a pass aimed at vulnerabilities rather than general quality.
Keep the human in the loop
Claude's review is a filter, not a verdict. It surfaces candidates fast, so the person approving the pull request spends their attention on judgment calls instead of hunting for a typo'd variable. Read its findings, discard the ones that miss context, and act on the rest.
The habit that pays off: review your own branch with /review before you request a human review. You fix the obvious things first, and the people you work with get a cleaner diff to think about.
Comments
Be the first to comment.