address-pr-review
Skill15 starsChanged 4 months agoMITView on GitHub
Look at the pull request review comments and address any issues raised.
6 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- novuhq/novutheir own version, first seen Nov 8, 2026
- teimurjan/skillstheir own version, first seen Nov 8, 2026
- timurgaleev/vibestacktheir own version, first seen Nov 8, 2026
- ian-pascoe/skillstheir own version, first seen Nov 1, 2026
- rxnew/agent-skillstheir own version, first seen Oct 11, 2026
- mnapoli/skillsedited, first seen Oct 3, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- mnapoli/skills★ 2171% same
Wrote their own version · 5
- novuhq/novu★ 40ksame name
- timurgaleev/vibestack★ 8same name
- ian-pascoe/skills★ 1same name
- rxnew/agent-skills★ 1same name
- teimurjan/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 9 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Run both helper scripts:
- Distinctive: line 30
If there are no unresolved threads and CI is green, stop here.
- Distinctive: line 34
If there are many items, create one task per item to keep things organized.
- Distinctive: line 38
Read the comment thread to understand the issue
- Distinctive: line 40
If a change is needed, make the necessary code changes
- Distinctive: line 44
Read the failure output to understand what broke
- Distinctive: line 49
After addressing all review comments and CI failures, commit your changes and push.
- Distinctive: line 53
After addressing each comment, reply using the helper script:
- Very specific: line 59
If the code was fixed as mentioned in the thread, reply with simply: "Fixed as suggested." and pass --resolve to mark the thread as …
- Very specific: line 60
If no change was applied, briefly explain why and keep the thread unresolved (omit --resolve) so the reviewer can reply if they disagree.
- Distinctive: line 61
Don't be unnecessarily verbose.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Step 1: Fetch unresolved review threads and CI status
Run both helper scripts:
bash ./get-unresolved-threads.shbash ./get-failing-ci.shThe first returns a JSON array of unresolved threads. Each thread has:
id— thread ID (needed to reply)path— file pathline/startLine— line numbers in the diffisOutdated— whether the diff has changed since the commentcomments.nodes[]— the comment thread (first = original comment, rest = replies), each withauthor.login,body, andurl
The second checks CI status and outputs failure details if any jobs failed (exit code 1 = failures, 0 = all passed).
If there are no unresolved threads and CI is green, stop here.
Step 2: Address each issue
If there are many items, create one task per item to keep things organized.
For each unresolved review thread:
- Read the comment thread to understand the issue
- Determine if a code change is needed, or if no change is needed (e.g. the comment is invalid or the suggestion is not appropriate)
- If a change is needed, make the necessary code changes
For each CI failure:
- Read the failure output to understand what broke
- Fix the code or tests to make CI pass
Step 3: Commit and push changes
After addressing all review comments and CI failures, commit your changes and push.
Step 4: Reply to each review thread
After addressing each comment, reply using the helper script:
bash ./reply-to-thread.sh "<thread_id>" "<body>" [--resolve]- If the code was fixed as mentioned in the thread, reply with simply: "Fixed as suggested." and pass
--resolveto mark the thread as resolved. - If no change was applied, briefly explain why and keep the thread unresolved (omit
--resolve) so the reviewer can reply if they disagree. - Don't be unnecessarily verbose.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

