Use when receiving code review feedback, before implementing suggestions - requires technical verification rather than 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
# Receiving Code Review
_Adapted from the MIT-licensed superpowers plugin by Jesse Vincent. See NOTICE.md._
## Overview
Code review requires technical evaluation, not emotional performance.
**Core principle:** verify every finding against the actual code before implementing it.
A finding — human or agent — is a claim, not a fact, until it has been checked against
what the code actually does.
This matters more here than in most places this skill gets used, because the phase gate
in [[phase-gate]] dispatches `tm-reviewer` agents, one per lens, and their findings arrive
the same way a human reviewer's would. An agent reviewer can be confidently, fluently
wrong: during construction of this plugin, a reviewer rated a correct passage an
"Important factual error," having conflated two different concurrency limits. Implementing
that finding as written would have introduced a defect. **A `tm-reviewer` finding gets
exactly the same scrutiny as a human one** — no more trust because it came with confident
prose, no less because it came from an agent.
## The Response Pattern
```
WHEN receiving a review finding (from a human or from tm-reviewer):
…
The line at the top of this page pins the label git:20260805.36003db, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_nqce7tyi5mirlc5o
GET https://markdownregistry.com/api/v1/resolve?ref=andreymudri/fleetmates/receiving-code-review
GET https://markdownregistry.com/api/v1/blob/bbe36651d5719e5cbdbd0e11e855c59f8de8cf370497f73f9189b1f0b409bd21
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.
andreymudri/fleetmates · skills/brainstorming/SKILL.md · Use when starting any creative work - creating features, building components, adding functionality, or modifying…
andreymudri/fleetmates · skills/executing-plans/SKILL.md · Use when you have a written implementation plan to execute inline in this session, with checkpoints - the non-fleet…
andreymudri/fleetmates · skills/finishing-a-development-branch/SKILL.md · Use when implementation is complete and needs integrating - re-runs the gate to verify each phase, then decides how the…
andreymudri/fleetmates · skills/fleet-lifecycle/SKILL.md · Use when spawning, listing, messaging, scaling, stopping, or resuming background teammates on a run.
andreymudri/fleetmates · skills/fleet-supervision/SKILL.md · Use when checking what a running fleet is doing - renders the digest, surfaces blocked or failed teammates, and…
andreymudri/fleetmates · skills/grilling/SKILL.md · Use when a plan, spec or design still has unresolved decisions, when the user says "grill me" or asks to be…
andreymudri/fleetmates · skills/parallel-execution/SKILL.md · Use when executing a written plan across background teammates - splits it into phases, dispatches worktree-isolated…
andreymudri/fleetmates · skills/phase-gate/SKILL.md · Use when a phase finished and needs an automated verdict before integration - runs command, agent, and MCP checks and…
andreymudri/fleetmates · skills/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - reproduce and isolate…
andreymudri/fleetmates · skills/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code - write the failing test first and…
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…
