code-review
code-review resolves a change set against a base commit, then runs three independent passes: Linus (data structures,
special cases, cost of generality), Uncle Bob (responsibility, dependency direction, naming), and Fowler (smells,
change locality, reversibility). The lenses are stances, not quotations.
When to use
Section titled “When to use”- “review this branch” or “would Linus approve this?”
- “is this abstraction worth it?” or “review this PR for design, not bugs”
It is not a defect hunt. Run tests, the type checker, and linters first.
Invoke
Section titled “Invoke”Run /code-review, or ask in plain words. It takes no arguments. The base is the commit, tag, or branch you name; on a
feature branch it is the merge base with the default branch; for uncommitted work it is HEAD.
What it produces
Section titled “What it produces”A report that leads with findings all three lenses agree on, then names each disagreement as a tradeoff with the condition that would resolve it. It changes no files.
Requirements
Section titled “Requirements”git only.
Example
Section titled “Example”/code-review review this branch against main for designMore detail: skill README.