Performs two-stage code reviews (spec compliance, then code quality) with severity-ranked findings. Use when asked to "review code", "review this PR", "check this diff", "review before merge", or mentions reviewing, auditing, or critiquing code changes, pull requests, or diffs.
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
## Two-Stage Review
**Stage 1 — Spec compliance** (do this FIRST): verify the changes implement what was intended. Check against the PR description, issue, or task spec. Identify missing requirements, unnecessary additions, and interpretation gaps. If the implementation is wrong, stop here — reviewing code quality on the wrong feature wastes effort.
**Stage 2 — Code quality**: only after Stage 1 passes, review for correctness, maintainability, security, and performance.
## Review Process
1. **Context** — read the PR description, linked issue, or task spec. Run the project's test/lint suite if available (`npm run test`, `make check`, etc.) to catch automated failures before manual review.
2. **Structural scan** — architecture, file organization, API surface changes. Flag breaking changes.
3. **Line-by-line** — correctness, edge cases, error handling, naming, readability. Use question-based feedback ("What happens if `input` is empty here?") instead of declarative statements to encourage author thinking.
4. **Security** — input validation, auth checks, secrets exposure, injection vectors (SQL, XSS, command). Flag race conditions (TOCTOU, check-then-act).
…
The line at the top of this page pins the label git:20260227.215f429, 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_efglqjqny2hqyjw3
GET https://markdownregistry.com/api/v1/resolve?ref=iliaal/whetstone/code-review
GET https://markdownregistry.com/api/v1/blob/8df0fba63db6ab1aaab7f8c79cbb4d63ddc849665e9b6f66626aadeabe36bd1d
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.
iliaal/whetstone · .agents/skills/audit-plugin/SKILL.md · Audit Whetstone skills, agents, and commands when asked for a plugin quality or consistency audit.
iliaal/whetstone · .agents/skills/diagnose-negatives/SKILL.md · Investigate negative session feedback for a Whetstone skill when asked to diagnose its failures.
iliaal/whetstone · .agents/skills/eval-skills/SKILL.md · Evaluate Whetstone skills from session evidence when asked to compare procedure-following results or optimization…
iliaal/whetstone · .agents/skills/skillopt/SKILL.md · Prepare or run Whetstone SkillOpt optimization when asked to optimize a process skill using SkillOpt.
iliaal/whetstone · .agents/skills/sync-from-repos/SKILL.md · Compare Whetstone with reference repositories when asked to sync cross-repository improvements.
iliaal/whetstone · .agents/skills/write-skill/SKILL.md · Author a new Whetstone plugin skill when asked to write a skill without upstream skills.sh sources.
agno-agi/agno · cookbook/02_agents/16_skills/sample_skills/code-review/SKILL.md · Code review assistance with linting, style checking, and best practices
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…
