Use when asked to review a pull request, a branch, a diff, staged changes or recent commits, check code before merging, or look for bugs in changes — any language.
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
## Overview
Find the defects that would hurt users or the team after merge, prove each with a concrete failing scenario, and keep everything else short. A review with three real bugs is worth more than thirty style notes.
## Method
1. **Get the change.**
- Branch: `git diff <base>...HEAD` (base = `main` unless told otherwise) and `git log <base>..HEAD --oneline`.
- Staged: `git diff --cached`. Pull request: `gh pr diff <number>`.
2. **Understand intent** from commit messages, PR description, and tests in the diff.
3. **Read beyond the hunk.** Open each changed function in full and its callers. Most bugs live where the change meets unchanged code.
4. **Hunt with the checklist**, category by category: [checklist.md](checklist.md).
5. **Verify each candidate.** Name the exact input or sequence that breaks it. If you cannot, drop it or mark it as a question.
6. **Report** using the contract below.
## Output contract
First line: a verdict — `Approve`, `Approve with nits`, or `Request changes` — and the count of findings by severity.
Then each finding, most severe first:
```
### [Blocker | Major | Minor] Title
- Location: path/file.ext:line
…
The line at the top of this page pins the label git:20261019.d667a4e, 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_euz2pkijwl5hgmov
GET https://markdownregistry.com/api/v1/resolve?ref=wst2002/claude-code-skills/code-review
GET https://markdownregistry.com/api/v1/blob/b29da6f24f7e8c7a75efcb6ed14ac1b21f07d79a12b0b36f990050b45ccf326d
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.
wst2002/claude-code-skills · plugins/proof-of-done/skills/proof-of-done/SKILL.md · Use before saying work is done, fixed, or complete after changing code. Run the project's checks, show their results…
wst2002/claude-code-skills · skills/accessibility-audit/SKILL.md · Use when checking a website, web app or UI component for accessibility, WCAG or a11y compliance, screen reader or…
wst2002/claude-code-skills · skills/api-design-review/SKILL.md · Use when designing a new REST API, reviewing endpoints, routes, controllers or an OpenAPI/Swagger spec, choosing status…
wst2002/claude-code-skills · skills/api-test-writer/SKILL.md · Use when writing automated API tests or integration tests for REST or GraphQL endpoints, testing from an…
wst2002/claude-code-skills · skills/architecture-diagram/SKILL.md · Use when asked to draw, diagram or visualize a system, codebase, architecture, data flow, request flow, database ERD…
wst2002/claude-code-skills · skills/bug-debugger/SKILL.md · Use when something is broken, a test fails, an error or stack trace appears, behavior is wrong or intermittent, a…
wst2002/claude-code-skills · skills/bug-report-writer/SKILL.md · Use when writing or improving a bug report, defect ticket or Jira/GitHub issue from notes, screenshots, logs, a video…
wst2002/claude-code-skills · skills/changelog-writer/SKILL.md · Use when writing release notes, a CHANGELOG.md entry, a version summary or "what's new" text from git history, merged…
wst2002/claude-code-skills · skills/codebase-onboarding/SKILL.md · Use when joining or exploring an unfamiliar codebase, asked to explain how a project works, where something is…
wst2002/claude-code-skills · skills/database-schema-design/SKILL.md · Use when designing a database from scratch, reviewing tables, an ERD, a Prisma/TypeORM/JPA/Django/SQLAlchemy schema or…
wst2002/claude-code-skills · skills/dependency-upgrade/SKILL.md · Use when upgrading packages, libraries, a framework or a language runtime (React, Next.js, Angular, Spring Boot…
wst2002/claude-code-skills · skills/dockerize-app/SKILL.md · Use when asked to dockerize or containerize an app, write or fix a Dockerfile or docker-compose.yml, shrink a large…
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…
cbrock84/headcount · plugins/technology/skills/code-review/SKILL.md · Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review…