resolve-pr-comments SKILL.md skillA
resolve-pr-comments from tobihagemann/turbo is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tobihagemann/turbo/resolve-pr-comments@git:20261023.44fa179Pins git:20261023.44fa179 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tobihagemann/turbo
- Path
codex/skills/resolve-pr-comments/SKILL.md- Versions recorded
- 13
- Latest version
- git:20261023.44fa179, committed Oct 23, 2026
- First version recorded
- Aug 1, 2026
- Size
- 18,164 bytes
- Repository stars
- 418
- License
- MIT
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using the rationale recalled from past Codex session history). Use when the user asks to "resolve PR comments", "fix review comments", "address PR feedback", "handle review comments", "address review feedback", "respond to PR comments", "answer review questions", or "address code review".
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 PR Review Comments Fetch unresolved review comments from a GitHub PR (inline threads, review-body observations, and issue-comment observations from the PR conversation), evaluate each one, fix or skip based on confidence, answer reviewer questions using the recalled rationale behind the change, and reply. Inline threads are answered with thread replies; issue-comment findings from people are answered with new PR conversation comments. Review-body findings and AI-reviewer issue comments flow through the same evaluate-and-fix pipeline; their outcomes land only in the summary. ## Task Tracking At the start, use `update_plan` to track each step, restating any remaining steps of a parent workflow alongside them: 1. Fetch comments 2. Triage already-addressed feedback 3. Run `$interpret-feedback` skill 4. Split questions and change requests 5. Run `$evaluate-findings` skill 6. Resolve ambiguities 7. Run `$resolve-findings` skill 8. Verify fixes 9. Answer reviewer questions 10. Wait for AI re-reviews 11. Run `$reply-to-pr-threads` skill 12. Run `$reply-to-pr-conversation` skill 13. Summary ## Step 1: Fetch Comments …
Read the whole file at its exact version.
How to install
mdr add tobihagemann/turbo/resolve-pr-comments@sha256:ee9386c4a2d9f5b4The line at the top of this page pins the label git:20261023.44fa179, 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_v3mnkixnyjnl44zc)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 13 versions of this file, between Aug 1, 2026 and Oct 23, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261023.44fa179 latest | 2026-10-23 | 44fa179 | 18,164 B | A | view · diff |
| git:20261019.db8371e | 2026-10-19 | db8371e | 18,008 B | A | view · diff |
| git:20261016.eff9821 | 2026-10-16 | eff9821 | 17,518 B | A | view · diff |
| git:20261014.915b660 | 2026-10-14 | 915b660 | 17,315 B | A | view · diff |
| git:20261007.4b9f4cf | 2026-10-07 | 4b9f4cf | 15,363 B | A | view · diff |
| git:20261006.5dd6e2e | 2026-10-06 | 5dd6e2e | 15,140 B | A | view · diff |
| git:20260930.42e6fe1 | 2026-09-30 | 42e6fe1 | 14,791 B | A | view · diff |
| git:20260927.f85642c | 2026-09-27 | f85642c | 14,780 B | A | view · diff |
| git:20260906.17c9fd0 | 2026-09-06 | 17c9fd0 | 14,543 B | A | view · diff |
| git:20260902.09607eb | 2026-09-02 | 09607eb | 14,001 B | A | view · diff |
| git:20260831.9985d29 | 2026-08-31 | 9985d29 | 13,327 B | A | view · diff |
| git:20260808.7a9ce3e | 2026-08-08 | 7a9ce3e | 13,347 B | A | view · diff |
| git:20260801.2ba5d2f | 2026-08-01 | 2ba5d2f | 12,496 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 (18164 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
tobihagemann/turbo · 418 stars · license MIT · pushed 2026-10-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_v3mnkixnyjnl44zc GET https://markdownregistry.com/api/v1/resolve?ref=tobihagemann/turbo/resolve-pr-comments GET https://markdownregistry.com/api/v1/blob/ee9386c4a2d9f5b455367031838ac966b143958b60e39923cb1536c99281af75
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 tobihagemann/turbo
Every file in tobihagemann/turbo