Review a change with independent read-only reviewers on requirements, project standards, and correctness. Use for a branch, a pull request, uncommitted work, or the review step of /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
# Review a change independently
Return verified findings, not edits. The caller owns corrections, tests, and
delivery; review authorizes no publication.
## 1. Fix what is reviewed
Identify the repository, the requirements (the Linear issue and the accepted
decisions, including the project's), and the exact comparison: base commit, head,
and any uncommitted or untracked files that belong to the change. Ask when the
base or the change's ownership is ambiguous rather than assume `main`. Keep
unrelated local work and secrets out of the review. Do not stage, commit, stash, or switch branches to obtain a diff, and
pause edits until the review returns.
## 2. Dispatch one reviewer per axis
| Axis | Compares the change with | Looks for |
| --- | --- | --- |
| Requirements | The issue and the accepted decisions | Missing, partial, wrong, or out-of-scope behavior |
| Standards | The project's instructions and documented conventions | Concrete violations with real impact |
| Correctness | The code, its callers, tests, and contracts | Bugs, regressions, failure handling, security and privacy risks |
…
The line at the top of this page pins the label git:20261101.951d650, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (2741 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
firzus/agent-skills · 4 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vemkyqroem43qaky
GET https://markdownregistry.com/api/v1/resolve?ref=firzus/agent-skills/code-review
GET https://markdownregistry.com/api/v1/blob/c9b9de92e767dcaeda9c45e39f449224fd605f256a08bf87a64f838add1a2c5c
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.
firzus/agent-skills · skills/engineering/authoring/SKILL.md · Use when creating, revising, or reviewing a skill's SKILL.md, supporting references, or templates, or when adjusting…
firzus/agent-skills · skills/engineering/chrome-devtools/SKILL.md · Debug and automate Google Chrome from the shell with the `chrome-devtools` CLI (npm package `chrome-devtools-mcp`)…
firzus/agent-skills · skills/engineering/gamification/SKILL.md · Gamification design for products, apps, and game meta-layers: design an engagement, habit, or retention system; choose…
firzus/agent-skills · skills/engineering/improve-architecture/SKILL.md · Find places where the code is costly to change and propose evidenced refactors that hide complexity behind smaller…
firzus/agent-skills · skills/engineering/instructions/SKILL.md · Use when creating, revising, or reviewing project AGENTS.md files, scoped rules, or other agent-facing documentation…
firzus/agent-skills · skills/engineering/monorepo/SKILL.md · Set up, evolve, and troubleshoot multi-project repositories. Use for workspace structure, cross-package dependencies…
firzus/agent-skills · skills/engineering/runbook/SKILL.md · Write an interactive bash runbook that guides a person through actions only they can take, such as copying credentials…
firzus/agent-skills · skills/engineering/security-review/SKILL.md · Perform source-only security audits of codebases, APIs, services, and applications. Use for security questions, focused…
firzus/agent-skills · skills/engineering/setup-harness/SKILL.md · Set up personal instructions for Codex (app and CLI), Cursor, or Claude Code, with reviewed content, native instruction…
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…
