code-review-checklist SKILL.md skillB
code-review-checklist from arasz/ai-badger is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add arasz/ai-badger/code-review-checklist@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- arasz/ai-badger
- Path
.ai-badger/skills/code-review-checklist/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.0, committed Aug 23, 2026
- First version recorded
- Aug 1, 2026
- Size
- 17,281 bytes
- Repository stars
- 3
- License
- MIT
Use when reviewing code — a PR, a diff, or freshly written changes — and you want concrete pass/fail checks rather than impressions. An aviation-style preflight checklist organised into sequential phases, with stack-specific items merged in from the project's config.
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 Preflight Checklist > **Pattern: Aviation preflight checklist.** Each phase is a system check. > Every item is a concrete, verifiable action — read it, check it, confirm it. > No item is skipped regardless of reviewer experience. Critical items carry > WARNING markers. Phases are sequential — complete each before proceeding. ## When to Use - Reviewing a PR before approving - Performing a milestone or sprint review - Self-reviewing before `git push` - Checking a subagent's output before merging ## When NOT to Use - Plan/spec feasibility review → `plan-review` - Frontend architecture deep-dive → `frontend-code-review` - Full milestone review methodology → `comprehensive-code-review` - Pre-commit security scan → `requesting-code-review` ## Preflight Protocol 1. **Read each item aloud** (or mentally). Verify against actual code, not assumptions. 2. **Mark PASS or FAIL.** If any FAIL exists, do not approve until resolved. 3. **WARNING items are non-negotiable.** They represent real bugs from past incidents. 4. **Complete phases sequentially.** Phase 1 gates all others. 5. **Report every FAIL in one shape** — item or rule / severity (Critical, High, Medium, Low) / …
Read the whole file at its exact version.
How to install
mdr add arasz/ai-badger/code-review-checklist@sha256:f2b98febe152b246The line at the top of this page pins the label v1.0.0, 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_q37nz3de6jb7lnvy)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 1, 2026 and Aug 23, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-23 | a32a56c | 17,281 B | B | view · diff |
| v1.0.0 | 2026-08-08 | 9006bf5 | 17,049 B | B | view · diff |
| v1.0.0 | 2026-08-07 | 4ef57e9 | 17,034 B | B | view · diff |
| v1.0.0 | 2026-08-07 | 013ee4d | 20,403 B | B | view · diff |
| v1.0.0 | 2026-08-01 | 81015a5 | 20,351 B | B | view |
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (17281 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
arasz/ai-badger · 3 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q37nz3de6jb7lnvy GET https://markdownregistry.com/api/v1/resolve?ref=arasz/ai-badger/code-review-checklist GET https://markdownregistry.com/api/v1/blob/f2b98febe152b246a9265ccecc8a254be521a165426688ca9bef6561582d62b0
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.