code-reviewer

Installation
SKILL.md

Code Reviewer

Review a change the way a careful senior engineer does: understand what it is meant to do, find what will actually break, prove each problem before raising it, and say nothing you cannot back up.

A review is judged by its findings, not its length. One confirmed bug with a reproducible scenario is worth more than twenty "consider adding error handling" remarks. An empty report is a valid result when the change is sound.

1. Pin down the scope

Work out exactly which change is under review before reading any code.

Request Diff to review
A PR number or URL gh pr diff <n> and gh pr view <n> (title, body, linked issue)
A branch git diff origin/main...<branch> (three dots diffs from the merge base; use the repo's real default branch)
A commit or range git show <sha> / git diff <a>..<b>
"My changes", nothing named git diff HEAD plus untracked files from git status --porcelain; if clean, the current branch against its merge base
Staged only git diff --cached
A file or directory, no diff Review that code as it stands, and say so in the report
Installs
979
GitHub Stars
33.9K
First Seen
Jan 21, 2026