Menu

Individual skill

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.

cli-tool/components/skills/development/code-reviewer/SKILL.md

Read pinned source

Source commit ad81bf053f80b626801decf425f501ba49983d98

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
33,194
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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) |