receiving-code-review SKILL.md skillA
receiving-code-review from jjuraszek/pi-gauntlet is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jjuraszek/pi-gauntlet/receiving-code-review@git:20261020.c79e361Pins git:20261020.c79e361 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jjuraszek/pi-gauntlet
- Path
skills/receiving-code-review/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261020.c79e361, committed Oct 20, 2026
- First version recorded
- May 28, 2026
- Size
- 6,692 bytes
- Repository stars
- 19
- License
- a license file GitHub does not identify
Use when receiving code review feedback from a human or external reviewer (GitHub review, human partner), before implementing suggestions, especially when feedback is unclear or technically questionable - verify, push back with evidence, never perform agreement; the subagent-driven-development review-fix loop is out of scope.
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
> **Related skills:** Verify each fix with `/skill:verification-before-completion`. Use `/skill:test-driven-development` for regression tests. # 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 ``` ## How to Respond **Never performative:** - ❌ "You're absolutely right!" / "Great point!" / "Thanks for catching that!" - ❌ "Let me implement that now" (before verification) **Instead:** - ✅ "Fixed. [Brief description of what changed]" - ✅ "Good catch - [specific issue]. Fixed in [location]." - ✅ Just fix it silently — the code shows you heard the feedback - ✅ Push back with technical reasoning if wrong - ✅ Ask clarifying questions if unclear …
Read the whole file at its exact version.
How to install
mdr add jjuraszek/pi-gauntlet/receiving-code-review@sha256:2928c0f982e34da4The line at the top of this page pins the label git:20261020.c79e361, 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_4rzxmelk7x2ta6fx)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between May 28, 2026 and Oct 20, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.c79e361 latest | 2026-10-20 | c79e361 | 6,692 B | A | view · diff |
| git:20261017.836bbce | 2026-10-17 | 836bbce | 6,518 B | A | view · diff |
| git:20260923.88370ec | 2026-09-23 | 88370ec | 6,238 B | A | view · diff |
| git:20260923.3292be0 | 2026-09-23 | 3292be0 | 6,083 B | A | view · diff |
| git:20260818.1338f94 | 2026-08-18 | 1338f94 | 6,555 B | A | view · diff |
| git:20260702.57334df | 2026-07-02 | 57334df | 6,412 B | A | view · diff |
| git:20260528.c4e4097 | 2026-05-28 | c4e4097 | 6,415 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6692 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
jjuraszek/pi-gauntlet · 19 stars · license a license file GitHub does not identify · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4rzxmelk7x2ta6fx GET https://markdownregistry.com/api/v1/resolve?ref=jjuraszek/pi-gauntlet/receiving-code-review GET https://markdownregistry.com/api/v1/blob/2928c0f982e34da44f16c0957e689ac525cf55820f635260d0b1f6fa8d90b86d
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.
More from jjuraszek/pi-gauntlet
Every file in jjuraszek/pi-gauntlet