receiving-code-review is agent-read markdown (skill) from ganyuanran/aegis: Use when receiving code review feedback before implementing suggestions, especially when feedback is unclear, risky, disputed, or technically questionable..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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 CLAUDE.md 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:**
```
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
A 17 of 17 checks passed. Deterministic, no model, 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 (6237 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
ganyuanran/aegis · 1,280 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rnemp24wpoyyn2jd
GET https://markdownregistry.com/api/v1/resolve?ref=ganyuanran/aegis/receiving-code-review
GET https://markdownregistry.com/api/v1/blob/7003bc2c29925aca762a32533d3b518bb1c00633990222c5280363042f91387f
Your agent 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.
ganyuanran/aegis · skills/brainstorming/SKILL.md · Use when defining ambiguous or high-complexity new features, product behavior, UI/component design, architecture…
ganyuanran/aegis · skills/communicating-concisely/SKILL.md · Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise…
ganyuanran/aegis · skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks without a written plan, with no conflicting shared mutable state or sequential…
ganyuanran/aegis · skills/establishing-project-context/SKILL.md · Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or…
ganyuanran/aegis · skills/executing-plans/SKILL.md · Use when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice…
ganyuanran/aegis · skills/finishing-a-development-branch/SKILL.md · Use when verified work needs integration or cleanup of an existing task-created branch/worktree, or the user explicitly…
ganyuanran/aegis · skills/first-principles-review/SKILL.md · Use when asked for first-principles or Occam's-razor review, or when high-risk decisions involve competing constraints…
ganyuanran/aegis · skills/goal-framing/SKILL.md · Use when the user explicitly sets an Aegis goal with /aegis-goal, Aegis goal:, or asks to define goal, success…
ganyuanran/aegis · skills/long-task-continuation/SKILL.md · Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before…
obra/superpowers · skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…
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…
coco-research/coco · 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…
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…
