Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
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
# Requesting Code Review
Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.
**Core principle:** Review early, review often.
## When to Request Review
**Mandatory:**
- After each task in subagent-driven development
- After completing major feature
- Before merge to main
**Optional but valuable:**
- When stuck (fresh perspective)
- Before refactoring (baseline check)
- After fixing complex bug
## How to Request
**1. Get git SHAs:**
```bash
BASE_SHA=$(git rev-parse HEAD~1) # or origin/main
HEAD_SHA=$(git rev-parse HEAD)
```
**2. Dispatch code reviewer subagent:**
Dispatch a `general-purpose` subagent, filling the template at [code-reviewer.md](code-reviewer.md)
**Placeholders:**
- `{DESCRIPTION}` - Brief summary of what you built
- `{PLAN_OR_REQUIREMENTS}` - What it should do
- `{BASE_SHA}` - Starting commit
- `{HEAD_SHA}` - Ending commit
**3. Act on feedback:**
- Fix Critical issues immediately
- Fix Important issues before proceeding
…
The line at the top of this page pins the label git:20260702.9dc0119, 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 (2826 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
jdanigo/hydraia · 8 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mcsxgzotpkmwowcl
GET https://markdownregistry.com/api/v1/resolve?ref=jdanigo/hydraia/requesting-code-review
GET https://markdownregistry.com/api/v1/blob/1017ccdd5bc61fab67c654cf118cbdb520464b313073a0a6b9a6b9aa647a3ad6
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.
jdanigo/hydraia · codex/skills/hydraia/SKILL.md · Codex-native hydraia pipeline. Use when the user asks to build, add, implement, or change a feature, brings a…
jdanigo/hydraia · skills/adr/SKILL.md · Use when a design decision is made that is expensive to reverse, affects multiple components, or rejects a plausible…
jdanigo/hydraia · skills/agency-tier-ui/SKILL.md · Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and…
jdanigo/hydraia · skills/api-design/SKILL.md · Use when designing or reviewing an API surface — REST, GraphQL, or gRPC. Contract-first methodology: the contract…
jdanigo/hydraia · skills/banner-design/SKILL.md · Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with…
jdanigo/hydraia · skills/brainstorming/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, or modifying…
jdanigo/hydraia · skills/caveman/SKILL.md · Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical…
jdanigo/hydraia · skills/db-optimization/SKILL.md · Use when the bottleneck is database-shaped — slow queries, lock timeouts, connection exhaustion, N+1 patterns, index…
jdanigo/hydraia · skills/design-to-code/SKILL.md · Elite render-to-code skill. The user brings a finished website design render (jpg/png); this skill distills it into…
obra/superpowers · skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
foryourhealth111-pixel/vibe-skills · bundled/skills/requesting-code-review/SKILL.md · Prepare and request a code review after implementation or before merge by assembling scope, requirements, git range…
a5c-ai/babysitter · library/methodologies/superpowers/skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
ganyuanran/aegis · skills/requesting-code-review/SKILL.md · Use when requesting independent code review, after implementation slices, before merging high-risk work, or when…
coco-research/coco · skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
