Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
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 Reception
## Overview
Code review requires technical evaluation, not emotional performance.
**Core principle:** Verify before implementing. Ask before assuming. Technical correctness over social comfort.
## The Response Pattern
```
WHEN receiving code review feedback:
1. READ: Complete feedback without reacting
2. UNDERSTAND: Restate requirement in own words (or ask)
3. VERIFY: Check against codebase reality
4. EVALUATE: Technically sound for THIS codebase?
5. RESPOND: Technical acknowledgment or reasoned pushback
6. IMPLEMENT: One item at a time, test each
```
## Forbidden Responses
**NEVER:**
- "You're absolutely right!" (explicit instruction-file violation)
- "Great point!" / "Excellent feedback!" (performative)
- "Let me implement that now" (before verification)
**INSTEAD:**
- Restate the technical requirement
- Ask clarifying questions
- Push back with technical reasoning if wrong
- Just start working (actions > words)
## Handling Unclear Feedback
```
IF any item is unclear:
STOP - do not implement anything yet
ASK for clarification on unclear items
WHY: Items may be related. Partial understanding = wrong implementation.
```
**Example:**
```
…
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 (6382 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_tt4igcowhuvvf5a3
GET https://markdownregistry.com/api/v1/resolve?ref=jdanigo/hydraia/receiving-code-review
GET https://markdownregistry.com/api/v1/blob/647036bbdab7bf2317e14e079595e984c9030f64295e2b4c0fb57dbeb48f25dd
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/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…
foryourhealth111-pixel/vibe-skills · bundled/skills/receiving-code-review/SKILL.md · Review-feedback handling route for CodeRabbit, GitHub, PR, or human reviewer comments. Use before implementing…
a5c-ai/babysitter · library/methodologies/superpowers/skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification…
ganyuanran/aegis · skills/receiving-code-review/SKILL.md · Use when receiving code review feedback before implementing suggestions, especially when feedback is unclear, risky…
coco-research/coco · skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…
jamditis/claude-skills-journalism · superjawn/skills/receiving-code-review/SKILL.md · Verifies review feedback with technical rigor, not blind agreement. Use when receiving review before implementing…
