address-pr-comments
Skill7 starsChanged 2 months agoMITView on GitHub
Use when implementing, responding to, or resolving GitHub pull request review feedback. Retrieves comments with get-pr-comments, applies requested changes, validates them, and optionally resolves addressed threads. Mutating actions require explicit confirmation.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- artberri/skillstheir own version, first seen Nov 8, 2026
- Pubx-ai/skillstheir own version, first seen Nov 8, 2026
- F3-Nation/f3-nationtheir own version, first seen Nov 2, 2026
- Cecilapp/Ceciltheir own version, first seen Oct 25, 2026
- Azure/azure-messaging-ai-contexttheir own version, first seen Oct 22, 2026
- microsoft/vscode-pull-request-githubtheir own version, first seen Oct 20, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- fallow-rs/fallow★ 5.3ksame name
- microsoft/vscode-pull-request-github★ 2.6ksame name
- Automattic/pocket-casts-ios★ 1.8ksame name
- Cecilapp/Cecil★ 299same name
- F3-Nation/f3-nation★ 210same name
- nex-agi/NexRL★ 119same name
- TangleML/tangle-ui★ 104same name
- SteveVitali/agent-skills★ 16same name
- Pubx-ai/skills★ 6same name
- gannonh/skills★ 2same name
7 more not listed
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.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- build-and-scan-container-imageSkill
- execute-database-migrationSkill
- generate-adrSkill
- generate-service-documentationSkill
- get-pr-commentsSkill
- incident-triageSkill
- install-dev-toolsSkill
- prepare-releaseSkill
- remediate-dependency-vulnerabilitiesSkill
- review-configurationSkill
- twg-agentic-searchSkill
- twg-artifactsSkill
- twg-code-reviewSkill
- twg-confluenceSkill
- twg-context-discoverySkill
- twg-engineering-workSkill
- twg-jira-resolve-merged-workSkill
- twg-jiraSkill
- twg-operational-healthSkill
- twg-responsibility-routingSkill
- twgSkill
- twg-space-creationSkill
- twg-status-rollupsSkill
- validate-and-deploy-iacSkill
- validate-and-deploy-kubernetesSkill
- validate-documentationSkill
- validate-github-actionsSkill
- verify-service-healthSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Read the affected code before editing.
- Distinctive: line 27
Run the narrowest relevant validation after each substantive edit.
- Distinctive: line 37
Never resolve a thread that was not addressed or intentionally declined.
- Distinctive: line 38
Do not apply reviewer suggestions blindly.
“Common” is measured: kept by at least 6 in 10 of the 16 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
Address Pull Request Comments
Turn pull request review feedback into validated changes. This skill owns the
write-side workflow; get-pr-comments owns read-only retrieval.
Parameters
owner,repository,pullRequest: target PR; default to the active PR.threadIds: specific threads; default to all unresolved threads.mode:implement,respond,resolve, ormerge-ready-check; defaultmerge-ready-check.autoApply: allow applying inline suggestions; defaultfalse.requireChecks: require passing checks; defaulttrue.format:summaryorjson; defaultsummary.
Workflow
- Retrieve unresolved feedback with
get-pr-comments. - Group comments by file, thread, and requested behavior.
- Read the affected code before editing; preserve unrelated changes.
- For
implement, make the smallest change that addresses the feedback. - Run the narrowest relevant validation after each substantive edit.
- Re-read the resulting diff and map every requested thread to a change, response, or explicit decision not to change it.
- Resolve threads or post replies only when the caller explicitly requests it.
- For
merge-ready-check, verify checks, approvals, conflicts, unresolved threads, and branch status without merging automatically.
Safety
- Never auto-merge.
- Never resolve a thread that was not addressed or intentionally declined.
- Do not apply reviewer suggestions blindly; inspect their context first.
- Preserve secrets and do not paste sensitive build output into PR comments.
Output
Return the PR identity, addressed threads, skipped threads with reasons, files changed, validation commands and results, remaining blockers, and next steps.
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.