review trained

The learned layer of the review guru: an evidence pass over a defined change, read-only by default, with fixes and replies as separate authorized mutations.

mental model

Review is an evidence pass over a defined change. Read the live project rules, the whole relevant diff, callers, and focused verification before reporting a defect. A review request alone is read-only; --fix and --reply are separate mutations.

examples

git status --short
git diff --check
git diff -- path/to/owned-file
git diff --cached -- path/to/owned-file

Use review-agent for defect-first findings, or review-pr for a GitHub PR. The PR guide separates read-only review, authorized fixes, and authorized replies.

best practices

Cite the smallest changed location that shows a reproducible issue. Distinguish observed failure, source-grounded risk, and missing test proof.
Review independently when a separate bounded perspective would help; a simple local change can be reviewed directly. The requesting guide is a delegation procedure, not a blanket mandate.
Preserve the current checkout and peer edits. Do not create a standards doc during a read-only review; report a missing contract as a finding.
Before a completion claim, run checks matched to the changed boundary. Git's diff documentation specifies --check for whitespace errors; it is only one narrow gate.

strengths

A precise defect-first review can catch regressions that green tests miss.
PR metadata, changed files, and project rules can establish the exact behavior being reviewed.

weaknesses / pain points

A diff alone may hide runtime state, migrations, or an authenticated path.
Reviewer subagents cost time and context; use a useful independent boundary.

gotchas

A missing standards document does not authorize creating one during a read-only review; report the missing contract if it matters.
Fixing a PR from another branch would require a checkout change. Verify current branch ownership before editing and ask only if that authority is missing.
--reply posts a message externally. Use only when the user explicitly authorized that communication.

known bugs

No version-specific review-tool defect is known here.