resolve-review-comments SKILL.md skillA
resolve-review-comments from leek/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add leek/agent-skills/resolve-review-comments@git:20261019.0f2f385Pins git:20261019.0f2f385 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- leek/agent-skills
- Path
skills/resolve-review-comments/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261019.0f2f385, committed Oct 19, 2026
- First version recorded
- Aug 16, 2026
- Size
- 6,237 bytes
- Repository stars
- 4
- License
- MIT
Triage, fix or rebut, then reply-and-resolve every review comment on a pull request, including AI-review bot findings (Codex, Copilot, Gemini). Use when the user wants to address, respond to, action, or clear the review comments on a PR.
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
# Resolve Review Comments Take every review comment on a pull request to a **resolved** end state: each one is either **fixed** (code changed, with a test) or **rebutted** (a one-line reason it is not a defect), then replied to and its thread resolved. No thread is left open and no finding is actioned on faith. A review comment is a claim, not an instruction. Bots (Codex, Copilot, Gemini) are confidently wrong often enough that **every finding earns its verdict from the code, the spec, the tests, and the permission model, never from the comment's own say-so.** ## 1. Gather every thread Resolve the repo (`gh repo view --json nameWithOwner`) and the PR number (from the argument, or `gh pr view --json number` for the current branch). Pull all three comment surfaces (reviews, inline review threads, general issue comments) and the PR's commit range. See [`references/gh-mechanics.md`](references/gh-mechanics.md) for the exact `gh api` and GraphQL calls; you need it whenever you touch the GitHub side. Completion criterion: a list of every unresolved thread, each with its comment id, GraphQL thread id, file:line, reviewed commit, and body. …
Read the whole file at its exact version.
How to install
mdr add leek/agent-skills/resolve-review-comments@sha256:3d08bb7edd92ab85The line at the top of this page pins the label git:20261019.0f2f385, 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_hyujkjdaxofugsej)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 16, 2026 and Oct 19, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.0f2f385 latest | 2026-10-19 | 0f2f385 | 6,237 B | A | view · diff |
| git:20261006.cae3ac3 | 2026-10-06 | cae3ac3 | 6,159 B | A | view · diff |
| git:20261005.870ecad | 2026-10-05 | 870ecad | 4,873 B | A | view · diff |
| git:20260922.be562dc | 2026-09-22 | be562dc | 4,872 B | A | view · diff |
| git:20260831.64fb3ee | 2026-08-31 | 64fb3ee | 4,802 B | A | view · diff |
| git:20260816.b3b3622 | 2026-08-16 | b3b3622 | 4,844 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 (6237 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
leek/agent-skills · 4 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hyujkjdaxofugsej GET https://markdownregistry.com/api/v1/resolve?ref=leek/agent-skills/resolve-review-comments GET https://markdownregistry.com/api/v1/blob/3d08bb7edd92ab851106503e20fa767a7db607733e5ff4736ad46f44dd15067b
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.