review-code SKILL.md skillA
review-code from yamanidev/claude-code-configuration is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yamanidev/claude-code-configuration/review-code@git:20260717.6d13f3cPins git:20260717.6d13f3c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yamanidev/claude-code-configuration
- Path
skills/review-code/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260717.6d13f3c, committed Jul 17, 2026
- First version recorded
- May 13, 2026
- Size
- 5,749 bytes
- Repository stars
- 9
- License
- MIT
Read-only workflow for code review, PR review, or feedback on a diff, branch, or specific files. Produces structured, prioritized feedback with blockers, should-fix items, nits, questions, and notable strengths — does not modify code. NOT for making changes (use /ship for that).
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 code You are a senior code reviewer. Your job is to produce structured, honest, prioritized feedback on someone else's code — not to rewrite it. Treat every review as if you'll be the one maintaining the result for the next two years. ## Operating principles 1. **Read-only by default.** A review produces feedback, not edits. Do not modify code unless the author explicitly asks for a fix. 2. **Understand the goal first.** If the intent of the change isn't obvious, ask before reviewing. A review without context is just opinions. 3. **Read beyond the diff.** Open the changed files in full, look at callers and adjacent code, and check the tests. Most real bugs hide in interactions, not in the lines that changed. 4. **Match the project's conventions.** "How we do it here" beats "how the textbook says". Compare against existing patterns before flagging style. 5. **Tier the feedback.** Don't bury a real bug under five style comments. 6. **Be specific.** File and line. Concrete failure mode. Not "consider improving error handling" — say *what* breaks *how*. …
Read the whole file at its exact version.
How to install
mdr add yamanidev/claude-code-configuration/review-code@sha256:63542afe48f21d22The line at the top of this page pins the label git:20260717.6d13f3c, 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_b2v2nox7ns6hmcc4)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 13, 2026 and Jul 17, 2026, about one every 16 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260717.6d13f3c latest | 2026-07-17 | 6d13f3c | 5,749 B | A | view · diff |
| git:20260604.f1c680b | 2026-06-04 | f1c680b | 6,030 B | A | view · diff |
| git:20260516.1cbb1a8 | 2026-05-16 | 1cbb1a8 | 4,889 B | A | view · diff |
| git:20260514.9f2878f | 2026-05-14 | 9f2878f | 4,556 B | A | view · diff |
| git:20260513.86b97c3 | 2026-05-13 | 86b97c3 | 4,551 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 (5749 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
yamanidev/claude-code-configuration · 9 stars · license MIT · pushed 2026-09-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_b2v2nox7ns6hmcc4 GET https://markdownregistry.com/api/v1/resolve?ref=yamanidev/claude-code-configuration/review-code GET https://markdownregistry.com/api/v1/blob/63542afe48f21d2286aff90351339df9c7a5f723d3fd67d5135618983fce683a
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 yamanidev/claude-code-configuration
Every file in yamanidev/claude-code-configuration