pr-comment-fix skillA
pr-comment-fix is agent-read markdown (skill) from j-star-films-studios/vibecode-protocol-suite: Automate fixing GitHub PR review comments. Use this skill whenever the user asks to "fix PR comments", "address review feedback", "resolve PR threads", or references a PR number/branch with unresolved review comments. Also trigger when the user says things like "go through the review comments on my PR", "handle the feedback on #123", or "clean up the review notes". Requires the `gh` CLI to be authenticated..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# PR Comment Fix Workflow
Checkout a PR branch, fetch unresolved review comments, fix each one, commit, reply, resolve, and push — all in one pass.
## Prerequisites
Before starting, verify `gh` is authenticated:
```bash
gh auth status
```
If it fails, stop and tell the user to run `gh auth login`.
## Step 1: Identify the PR
Determine the target PR from the user's message. They might give you a PR number (`#142`), a branch name (`feature/new-parser`), or a URL. Normalize to a PR number early:
```bash
# If given a branch name, find its open PR
gh pr list --head <branch-name> --state open --json number --jq '.[0].number'
```
Once you have the PR number, fetch the branch name and check it out:
```bash
gh pr checkout <pr-number>
```
This ensures you're on the exact branch the PR tracks — not a stale local copy.
## Step 2: Fetch unresolved review comments
Pull all review comments and filter to unresolved threads. Each comment has a thread ID, file path, line number, and body.
```bash
gh api graphql -f query='
query($owner: String!, $repo: String!, $pr: Int!) {
repository(owner: $owner, name: $repo) {
pullRequest(number: $pr) {
…Read the whole file at its exact version.
How to install
mdr add j-star-films-studios/vibecode-protocol-suite/pr-comment-fix@git:20260820.4dbe9e4mdr add j-star-films-studios/vibecode-protocol-suite/pr-comment-fix@sha256:8cd3976399e66fabPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_xczfnudo6nelmgnp)
1 badge views in 30 days
Versions
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 (6615 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
j-star-films-studios/vibecode-protocol-suite · 24 stars · license ISC · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xczfnudo6nelmgnp GET https://markdownregistry.com/api/v1/resolve?ref=j-star-films-studios/vibecode-protocol-suite/pr-comment-fix GET https://markdownregistry.com/api/v1/blob/8cd3976399e66fab1df1262e4a37e8f1794d513991ed8ef99e814054d32d8e6b
Your agent 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.