code-review-response SKILL.md skillA
code-review-response from khaledsaeed18/dotclaude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add khaledsaeed18/dotclaude/code-review-response@git:20260921.3a2f779Pins git:20260921.3a2f779 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- khaledsaeed18/dotclaude
- Path
.claude-plugin/plugins/engineering/skills/code-review-response/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260921.3a2f779, committed Sep 21, 2026
- First version recorded
- Jul 4, 2026
- Size
- 3,569 bytes
- Repository stars
- 5
- License
- MIT
Process code-review feedback with technical rigour. Understand each point, check it against the actual codebase, and respond with reasoning or implementation rather than reflexive agreement. Use when you receive review comments (from a human, the code-reviewer agent, or any reviewer) and are about to act on them, especially if any feedback seems unclear or wrong.
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 is a technical exchange, not a social one. The job isn't to agree warmly and start changing things; it's to understand each point, verify it against the real code, and then implement it, push back on it, or ask about it on the merits. Blindly applying a suggestion that's wrong for this codebase is as much a failure as ignoring a good one. ## The response pattern For each piece of feedback: 1. **Read it fully** before reacting. Take in all of it, not just the first comment. 2. **Restate the point** in your own words, or ask, if you can't. If you can't articulate what's being asked, you can't correctly implement it. 3. **Verify against reality.** Check the claim against the actual codebase. Is the problem real here? Does the suggested approach fit how this code already works? 4. **Evaluate on technical merit.** Is it sound *for this codebase*, not just in the abstract? 5. **Respond.** A technical acknowledgement, a clarifying question, or reasoned pushback, whichever the evaluation produced. 6. **Implement one item at a time**, verifying each before moving to the next. ## Skip the performance …
Read the whole file at its exact version.
How to install
mdr add khaledsaeed18/dotclaude/code-review-response@sha256:8ed3950e4db7b99eThe line at the top of this page pins the label git:20260921.3a2f779, 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_vi5sknkwmrilipdx)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 4, 2026 and Sep 21, 2026, about one every 27 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.3a2f779 latest | 2026-09-21 | 3a2f779 | 3,569 B | A | view · diff |
| git:20260921.6c17ffd | 2026-09-21 | 6c17ffd | 3,279 B | A | view · diff |
| git:20260921.36d6832 | 2026-09-21 | 36d6832 | 3,303 B | A | view · diff |
| git:20260704.5149f4c | 2026-07-04 | 5149f4c | 3,306 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 (3569 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
khaledsaeed18/dotclaude · 5 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vi5sknkwmrilipdx GET https://markdownregistry.com/api/v1/resolve?ref=khaledsaeed18/dotclaude/code-review-response GET https://markdownregistry.com/api/v1/blob/8ed3950e4db7b99e99e9a920067a71afebc237c707294e8f234e5b870824dce0
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 khaledsaeed18/dotclaude
Every file in khaledsaeed18/dotclaude