receiving-code-review skillA
receiving-code-review is agent-read markdown (skill) from yeaight7/agent-powerups: Use when receiving code review feedback, before implementing suggestions — requires technical verification and reasoned pushback, not performative agreement or blind implementation..
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
## Purpose Evaluate code review feedback with technical rigor before implementing any changes. Prevents wasted work from blindly applying incorrect suggestions and maintains technical integrity. ## When to Use - Receiving code review comments from any reviewer (human or automated). - Feedback seems unclear or technically questionable. - Multiple review items arrive at once and need to be prioritized. ## Inputs - Code review feedback (comments, suggestions, required changes). - Access to the codebase to verify claims. ## Workflow ``` 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 ``` ### Handling Unclear Feedback If any item is unclear: stop, ask for clarification on all unclear items before implementing anything. Items may be related — partial understanding leads to wrong implementation. ### Feedback from the User (Project Owner) - Trusted — implement after understanding. - Still ask if scope is unclear. …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/receiving-code-review@git:20260606.5a149c7mdr add yeaight7/agent-powerups/receiving-code-review@sha256:4054cc5c58a63702Pin 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.
[](https://markdownregistry.com/a/art_ihm3n74adafkhqeo)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.5a149c7 latest | 2026-06-06 | 5a149c7 | 4,035 B | A | view · diff |
| git:20260502.728c0e7 | 2026-05-02 | 728c0e7 | 4,033 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 (4035 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
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ihm3n74adafkhqeo GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/receiving-code-review GET https://markdownregistry.com/api/v1/blob/4054cc5c58a6370290a8e15631da483124bd7e143046a6bb85ae17005a40b6fe
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.
More from yeaight7/agent-powerups
Every file in yeaight7/agent-powerups