respond-to-review SKILL.md skillA
respond-to-review from chrislacey89/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chrislacey89/skills/respond-to-review@git:20261105.863eae4Pins git:20261105.863eae4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chrislacey89/skills
- Path
respond-to-review/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261105.863eae4, committed Nov 5, 2026
- First version recorded
- Oct 27, 2026
- Size
- 28,813 bytes
- Repository stars
- 4
- License
- MIT
Side-route for when a teammate's review lands on your open PR and you want to decide what to fix, what to push back on, and what to defer. Each thread's claim is checked against the code by a fresh sub-agent before you decide, threads you mark fix go to /fix-findings, pushback gets a reply draft you post yourself, and a record stays in the project's sidecar so you can come back to it. Not for reviewing someone else's PR (that's /pre-merge --pr), not for the pack's own review findings…
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
# Respond to Review Take a teammate's review of your PR, check each comment's claim against the code with a reader who did not write it, let the human decide what happens to each one, hand the fixes to `/fix-findings`, draft the pushback, and leave a record in the project's sidecar to come back to. ## Why this skill exists On a team, most PRs get a human review after `/pre-merge` has stamped them. Before this skill, the pack had no route for that review. `/pre-merge` writes `.claude/.review-stamped` beside its stamp, the post-review edit lock then refuses implementation edits unless `/fix-findings` is running, and `/fix-findings` accepted only findings from a `/pre-merge` run. A teammate's comment was neither, so the only way to act on it was to delete the lock by hand and fix in the session that wrote the code. Sending those comments straight into `/fix-findings` would have been the wrong repair. Its fixer is briefed to fix, and reports `refuted` only when the tree flatly contradicts a claim. A comment that is accurate but wrong in judgment, a preference phrased as a requirement, or a request outside the PR's scope would …
Read the whole file at its exact version.
How to install
mdr add chrislacey89/skills/respond-to-review@sha256:a4ea44c4c66d56bbThe line at the top of this page pins the label git:20261105.863eae4, 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_rxt6uuzgo63lqzia)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 27, 2026 and Nov 5, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261105.863eae4 latest | 2026-11-05 | 863eae4 | 28,813 B | A | view · diff |
| git:20261105.01fdd6e | 2026-11-05 | 01fdd6e | 28,049 B | A | view · diff |
| git:20261031.174277f | 2026-10-31 | 174277f | 28,035 B | A | view · diff |
| git:20261028.eb646fd | 2026-10-28 | eb646fd | 27,555 B | A | view · diff |
| git:20261027.aaf039e | 2026-10-27 | aaf039e | 18,304 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 (28813 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
chrislacey89/skills · 4 stars · license MIT · pushed 2026-11-06 · branch prod
API
GET https://markdownregistry.com/api/v1/artifacts/art_rxt6uuzgo63lqzia GET https://markdownregistry.com/api/v1/resolve?ref=chrislacey89/skills/respond-to-review GET https://markdownregistry.com/api/v1/blob/a4ea44c4c66d56bb2cc3ee79f7e67e87c5a63eedb10ae42ec71eab29acedb938
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.