code-review SKILL.md skillA
code-review from leek/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add leek/agent-skills/code-review@git:20261012.631a831Pins git:20261012.631a831 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- leek/agent-skills
- Path
skills/code-review/SKILL.md- Versions recorded
- 8
- Latest version
- git:20261012.631a831, committed Oct 12, 2026
- First version recorded
- Aug 18, 2026
- Size
- 11,470 bytes
- Repository stars
- 4
- License
- MIT
Three-axis review of the diff since a fixed point: Correctness (bugs, failure modes, security), Standards (repo conventions) and Spec (ticket/PRD fidelity). Use when the user wants to review a branch, PR, WIP changes, or asks to "review since X".
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 Three-axis review of the diff between `HEAD` and a fixed point the user supplies: - **Correctness**: would this change break something? Bugs, failure modes (what a side effect does when it fails, repeats, or races), security, data, broken contracts, missing tests. - **Standards**: does the code conform to how this repo writes code? - **Spec**: does the code faithfully implement the originating ticket / PRD / spec? The axes run **separately** so they don't pollute each other's context, then this skill aggregates their findings. Prefer **parallel sub-agents** when the harness supports them; otherwise run the reviews **inline in sequence** in this session. Either path must finish every axis before aggregating: never leave a review handle running past session end. ## Process ### 1. Pin the fixed point Whatever the user said is the fixed point: a commit SHA, branch name, tag, `main`, `HEAD~5`, etc. If they didn't specify one, ask for it (when invoked from `implement`, it's the ticket's base commit). …
Read the whole file at its exact version.
How to install
mdr add leek/agent-skills/code-review@sha256:c3c6d126b96281daThe line at the top of this page pins the label git:20261012.631a831, 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.
[](https://markdownregistry.com/a/art_7agjjfqinziy3miu)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between Aug 18, 2026 and Oct 12, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.631a831 latest | 2026-10-12 | 631a831 | 11,470 B | A | view · diff |
| git:20261006.5b17497 | 2026-10-06 | 5b17497 | 10,942 B | A | view · diff |
| git:20261006.cae3ac3 | 2026-10-06 | cae3ac3 | 10,890 B | A | view · diff |
| git:20261004.4e9b2df | 2026-10-04 | 4e9b2df | 10,455 B | A | view · diff |
| git:20260922.600ab82 | 2026-09-22 | 600ab82 | 9,498 B | A | view · diff |
| git:20260922.be562dc | 2026-09-22 | be562dc | 9,223 B | A | view · diff |
| git:20260831.64fb3ee | 2026-08-31 | 64fb3ee | 9,079 B | A | view · diff |
| git:20260818.00f1f2e | 2026-08-18 | 00f1f2e | 9,183 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11470 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
leek/agent-skills · 4 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7agjjfqinziy3miu GET https://markdownregistry.com/api/v1/resolve?ref=leek/agent-skills/code-review GET https://markdownregistry.com/api/v1/blob/c3c6d126b96281da1616db0fa5339bfbe0a37dcc3e0536bf12cefe0c63651452
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from leek/agent-skills
Every file in leek/agent-skills