Reviewing code for defects: diff-first reading, severity classification, evidence over inference, finding caps, and terminal verdicts. Use when reviewing a diff, PR, or patch, or auditing someone else's work.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Code review
The same practice for any agent: reviewing a diff, a patch, or another agent's work.
## Read the diff first
- `git diff <base>..<head>` (or the PR's diff) IS the review. Read the tree only where the diff raises a question you can state.
- Open a file when you can name the question it answers; re-reading files you already read is waste.
- Review what changed plus what it touches: callers, shared state, and the tests near the change.
## Classify every finding
| Severity | Means |
|---|---|
| BLOCKER | Wrong, unsafe, or loses data. Ship it and something breaks. |
| MAJOR | A real defect or missing case that will bite, but not stop-ship. |
| MINOR | Correctness-preserving improvement. |
| NIT | Style, naming, wording. |
- Caps: at most 5 MINOR and 5 NIT per round, the highest-value ones. A long tail of nits buries the blockers and costs a remediation round to answer.
- Severity is about consequence, not effort to fix. Do not inflate; do not deflate to avoid an awkward round.
## Evidence over inference
- Every finding carries a location: file, line, and the code path. Without one it is a lead, not a finding.
…
The line at the top of this page pins the label git:20261012.3e10f8e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_ot6iyr43ffimnom6
GET https://markdownregistry.com/api/v1/resolve?ref=damianvtran/local-operator/code-review
GET https://markdownregistry.com/api/v1/blob/2147f8a67d7b73e52158c66fc29622e3c06f06f2f5a0e28889717ed01f1989db
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
damianvtran/local-operator · local_operator/skills/builtin/browser-qa/SKILL.md · Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console…
damianvtran/local-operator · local_operator/skills/builtin/design-qa/SKILL.md · Deterministic design review for UI/UX on web and terminal screens: measure contrast, spacing, overlap, clipping and…
damianvtran/local-operator · local_operator/skills/builtin/financial-analysis/SKILL.md · Financial figures done carefully: periods and fiscal calendars, units and currencies, reconciliation, magnitude sanity…
damianvtran/local-operator · local_operator/skills/builtin/frontend-design/SKILL.md · Designing interfaces with a deliberate point of view: plan before pixels, avoid the generic-default look, typography…
damianvtran/local-operator · local_operator/skills/builtin/scheduling/SKILL.md · Scheduling across time zones: confirm times in the attendee's own zone, use IANA zone names, mind DST edges, buffers…
damianvtran/local-operator · local_operator/skills/builtin/test-driven-development/SKILL.md · Writing code with tests first: RED-GREEN-REFACTOR, reproduce bugs as failing tests before fixing, and avoid testing…
kyegomez/swarms · examples/single_agent/capabilities/skills/multiple_skill_dirs/team_skills/code-review/SKILL.md · Review Python code for bugs, missing tests and security issues using the team's shared standards
basicmachines-co/basic-memory · .agents/skills/code-review/SKILL.md · Use when reviewing Basic Machines code for house style, architecture risk, pre-merge hardening, or whether a change…
nteract/semiotic · .github/skills/code-review/SKILL.md · Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence. Use for GitHub…
cbrock84/headcount · plugins/technology/skills/code-review/SKILL.md · Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review…
