responding-to-review SKILL.md skillA
responding-to-review from grit-77/done-is-a-claim is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add grit-77/done-is-a-claim/responding-to-review@git:20261011.a0f0c71Pins git:20261011.a0f0c71 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- grit-77/done-is-a-claim
- Path
skills/responding-to-review/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261011.a0f0c71, committed Oct 11, 2026
- Size
- 4,325 bytes
- Repository stars
- 33
- License
- Apache-2.0
Resolve incoming code-review feedback against the current revision and user contract. Use to assess comments, implement authorized fixes, explain supported disagreement and verify item status; review does not authorize posting replies.
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
# Responding to review Treat a comment as a claim to investigate. Resolve supported findings and retain the evidence for decisions; neither the author's confidence nor a reviewer's authority establishes the current behavior. ## Bind each item to the candidate Read the original outcome, acceptance and preservation requirements, current revision, dirty inputs, diff and file ownership. Locate each comment's referenced revision and code. A finding on an old patch may remain relevant, so inspect its current equivalent before dismissing it or applying an obsolete suggestion. Keep a compact per-item record: comment identifier, current code locator, classification, supporting observation, next action and status. Use these classes: - **Substantiated:** current evidence shows a contract defect. - **Stale:** the referenced issue no longer exists on the current candidate. - **Disputed:** the proposed change conflicts with the contract or current evidence. - **Unclear:** missing information materially affects what correction is valid. - **Scope proposal:** useful new behavior or preference beyond the agreed outcome. …
Read the whole file at its exact version.
How to install
mdr add grit-77/done-is-a-claim/responding-to-review@sha256:00dc3569f74abf0dThe line at the top of this page pins the label git:20261011.a0f0c71, 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_xxkqp6dtfjcbxmxj)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 11, 2026.
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 (4325 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
grit-77/done-is-a-claim · 33 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xxkqp6dtfjcbxmxj GET https://markdownregistry.com/api/v1/resolve?ref=grit-77/done-is-a-claim/responding-to-review GET https://markdownregistry.com/api/v1/blob/00dc3569f74abf0d5e199e8e67886607f6d969b009896fa69fd3466e63b90b4f
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 grit-77/done-is-a-claim
Every file in grit-77/done-is-a-claim