Request or perform a git-backed code review for a defined diff or SHA range using implementation context and requirements. Use when finishing a task, completing a major feature, preparing to merge, or when you need a fresh review before proceeding.
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
Request or perform code review before issues compound.
## Operating Mode
Act as a pragmatic review coordinator first, and a reviewer second.
Prioritize:
- clear review scope before opinions
- requirement alignment before style nits
- bugs and regressions before polish
- explicit evidence before confidence
Review early and review often.
## Workflow
Follow this sequence unless the user asks for only one part of the review flow.
### 1. Define the review scope
Choose the smallest meaningful diff to review.
Prefer:
- branch review: `git merge-base origin/main HEAD` to `HEAD`
- task review: previous task commit to `HEAD`
- single-commit review: `HEAD~1` to `HEAD`
Use commands such as:
```bash
git merge-base origin/main HEAD
git rev-parse HEAD
git log --oneline --decorate -n 10
```
If the change set is too large or mixes unrelated work, call that out and split the review scope before continuing.
### 2. Gather review context
Capture the minimum context a reviewer needs:
- what was implemented
- plan, requirements, or acceptance criteria
- known risks or edge cases
- tests added, updated, or still missing
- exact `BASE_SHA` and `HEAD_SHA`
…
The line at the top of this page pins the label git:20260328.a91fb8e, 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 (4655 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
flc1125/skills · 39 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cmgvgq2yi4xgmtmo
GET https://markdownregistry.com/api/v1/resolve?ref=flc1125/skills/code-review
GET https://markdownregistry.com/api/v1/blob/1e28ede7a485e22c077561518108910e7cd172ed128e93fdd0d4a2e5fbba251e
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.
flc1125/skills · skills/async/SKILL.md · Launch and coordinate Codex subagents as deferred tasks. Use when the user wants to start bounded subagent work now…
flc1125/skills · skills/eli5/SKILL.md · Create a simple, picture-first explanation of a topic, defaulting to self-contained HTML. Use when the user says ELI5…
flc1125/skills · skills/engineering-backend-architect/SKILL.md · Design backend system architecture for new products, large features, platform refactors, API and database design…
flc1125/skills · skills/experts/SKILL.md · Assemble a panel of experts to assess a problem from multiple professional perspectives, surface agreement and…
flc1125/skills · skills/getnote/SKILL.md · Save, search, list, and organize Get 笔记 notes, images, tags, and knowledge resources through the Get 笔记 OpenAPI. Use…
flc1125/skills · skills/github-create-pr/SKILL.md · Create GitHub pull requests from a local branch using a reviewable workflow for branch checks, diff analysis, PR…
flc1125/skills · skills/github-renovate-prs/SKILL.md · Inspect, triage, approve, and merge GitHub Renovate pull requests with gh. When no repository is provided, use the…
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…
