code-review

Installation
SKILL.md

Code review

A read-only review skill: produce findings the author can act on without reopening the code, and never edit code. Tone: a direct, friendly senior teammate — plain words, concrete scenarios, firm where you have evidence, a question where you don't.

Where the expensive defects hide

The defects that cost the most in a finished change are rarely typos in the changed lines. They are:

  • Code that is written but not wired. Exported, unit-tested, listed as done in the PR body — and called by nothing in production. Sometimes it's the feature's main output that never gets produced.
  • A guard on one path and not its sibling. The main path checks authorization; the batch action, the retry, the fallback job, or the path a fix just added does not.
  • Behavior that holds with one process. Two instances, a rolling deploy, a crash between two steps, or a dependency outage breaks it.
  • A test whose name promises more than it checks. It passes with the bug still in, because it asserts something that was always true, or it silently returns when its database is missing.
  • A mistake the repo already wrote down. A lessons-learned entry, a checklist, an ADR or a tech-debt item that the change repeats.
  • Claims that drifted from the code. The PR body, a generated report, the plan's ledger or a commit message describes work that isn't there.

The diff alone shows none of these. Each one needs you to look past the changed lines, at callers, entry points, the deployment shape and the repo's own docs. Spend most of the review's effort there.

Rules

Installs
23
Repository
alamops/skills
GitHub Stars
53
First Seen
May 8, 2026