code-reviewer
You MUST use this when asked to review code: a pull request, a branch, a commit, staged or uncommitted changes, or "check this before I merge". Scopes the review to the diff, reads the surrounding code, hunts for real bugs (correctness, security, data loss, concurrency, broken callers, missing tests), verifies every finding against the code before reporting it, and returns a short severity-ranked list with a concrete failure scenario for each. Use it for any language; not for writing new code or for style-only cleanups.
Target: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Code Reviewer
- 1. Pin down the scope
- 2. Understand the intent
- 3. Read beyond the hunks
- 4. Hunt
- 5. Verify every finding
- 6. Rank by severity
- 7. Report
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. Work out exactly which change is under review before reading any code. | Request | Diff to review | |---|---| | A PR number or URL | gh pr diff and gh pr view (title, body, linked issue) | | A branch | git diff origin/main... (three dots diffs from the merge base; use the repo's real default branch) | | A commit or range | git show / git diff .. | | "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 | Then: Run git diff --stat on the same range (for a PR, gh pr view --json files,additions,deletions) to see the size and the files touched. Make sure e
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- davila7/claude-code-templates
- Source file
- cli-tool/components/skills/development/code-reviewer/SKILL.md
- Fixed revision
- 21be197f100a12b8d0dd9a211cc244c8179f84d3
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: davila7/claude-code-templates · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T14:01:44.213Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.