Reviews a change — a diff, a PR, a branch, or uncommitted work — for correctness, risk, and maintainability, and reports findings ranked by severity. Use this whenever the user asks you to review, check over, or give feedback on code they or someone else wrote, mentions a pull request, or says a change is "ready", even if they only ask "does this look ok?". For examining a whole codebase rather than a change, use code-analysis; for vulnerabilities specifically, use security-analysis.
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
A review is a search for the ways this change fails in production, ranked by how badly. It is
not a style pass. Style is the lint job's work — if you spend the review on formatting, you
have used up the reader's attention on the cheapest possible findings.
The bar for reporting: **could you write the input that makes this go wrong?** If not, you have
a question, not a finding. Say it as a question.
## 1. Understand the intent before reading the diff
Read the PR description, linked issue, or ask. Reviewing a change without knowing its goal
produces suggestions that fight the author's purpose.
Then decide what *should* have changed. Files you expected to see and don't are the highest-
yield finding in any review — a new state field with no migration, a new branch with no test,
a new error path with no logging.
**Done when:** you can state the intent in a sentence, and you have a list of what you expect
the diff to touch.
## 2. Read the change in dependency order
Not top to bottom, and not alphabetically, the order the tool shows you is meaningless. Start
at the data model or interface, then the logic, then the callers, then the tests. Meaning flows
…
The line at the top of this page pins the label git:20260828.866dec6, 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 (5244 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
okhp3/skillz · 3 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_npj75mbmit6uosdi
GET https://markdownregistry.com/api/v1/resolve?ref=okhp3/skillz/code-review
GET https://markdownregistry.com/api/v1/blob/baec0f167ab64243ac0bc74048e566d3f194d9a9f91b2913c57ea1cc8fb295d4
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.
okhp3/skillz · .agents/skills/architecture-decision-records/SKILL.md · Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation…
okhp3/skillz · .agents/skills/frontend-design/SKILL.md · Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to…
okhp3/skillz · .agents/skills/okhp3-artifact-validation/SKILL.md · Validate a project change, draft, research packet, skill, promotion package, or handoff before it is treated as…
okhp3/skillz · .agents/skills/okhp3-as-is-process-capture/SKILL.md · Capture and normalise a current-state process description into a structured as-is process YAML with stable step…
okhp3/skillz · .agents/skills/okhp3-brand-style-registry/SKILL.md · OverKill Hill P³ visual style registry and application workflow. Use when a user wants to extract a reusable brand…
okhp3/skillz · .agents/skills/okhp3-capture-intake/SKILL.md · Preserve one raw idea, file, link, transcript, or request in a project inbox with provenance and minimal handling. Use…
okhp3/skillz · .agents/skills/okhp3-custom-gpt-builder/SKILL.md · Build, audit, and improve OpenAI Custom GPTs with production-grade methodology. Use this skill when the user asks to…
okhp3/skillz · .agents/skills/okhp3-custom-gpt-readiness/SKILL.md · Assess an incomplete or newly proposed Custom GPT concept for build readiness. Use when a user has a GPT idea, partial…
okhp3/skillz · .agents/skills/okhp3-decision-model-authoring/SKILL.md · Author and validate decision models from PNS decision points using DMN-aligned rule tables. Use this skill when the PNS…
okhp3/skillz · .agents/skills/okhp3-elicitation-interviews/SKILL.md · Plan and facilitate structured elicitation sessions using BABOK v3 interview and workshop techniques. Use this skill…
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…
