address-pr-feedback
Skill0 starsChanged 2 months agoMITView on GitHub
Address review comments on a pull request: triage, implement fixes, push, reply on threads.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- SDSLeon/lightcodetheir own version, first seen Nov 1, 2026
- Porabuild/Poracodetheir own version, first seen Nov 1, 2026
- ericmasiello/skillstheir own version, first seen Oct 20, 2026
- codemonkey85/PKMDS-Blazortheir own version, first seen Oct 8, 2026
- JeffreyFerreiras/ai-skillstheir own version, first seen Oct 5, 2026
- IcodeNet/agent-skillstheir own version, first seen Jul 10, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- codemonkey85/PKMDS-Blazor★ 240same name
- Porabuild/Poracode★ 121same name
- SDSLeon/lightcode★ 121same name
- JeffreyFerreiras/ai-skills★ 1same name
- ericmasiello/skills★ 0same name
- IcodeNet/agent-skills★ 0same 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.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/CLAUDE.mdcCursor rule
- .cursor/rules/code-style.mdcCursor rule
- .cursor/rules/docker-compose-local.mdcCursor rule
- .cursor/rules/github-cli-pr.mdcCursor rule
- .cursor/rules/git.mdcCursor rule
- .cursor/rules/git-worktree.mdcCursor rule
- .cursor/rules/ticket-driven-workflow.mdcCursor rule
- agentic-e2eSkill
- close-ticketSkill
- docs-app-syncSkill
- review-dependabot-prSkill
- screen-to-specSkill
- spec-lookupSkill
- spec-to-screenSkill
- start-ticketSkill
- address-pr-feedbackSkill
- agentic-e2eSkill
- close-ticketSkill
- docs-app-syncSkill
- review-dependabot-prSkill
- screen-to-specSkill
- spec-lookupSkill
- spec-to-screenSkill
- start-ticketSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
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 26
Commit with explicit staging.
“Common” is measured: kept by at least 6 in 10 of the 6 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 PR feedback
PR number: $ARGUMENTS
Step 1: Gather feedback
gh pr view $ARGUMENTSgh pr diff $ARGUMENTSgh api "/repos/$(gh repo view --json nameWithOwner -q .nameWithOwner)/pulls/$ARGUMENTS/comments"- Review threads and checklist items from CI if any.
Step 2: Triage
Classify each comment: must-fix / question / nit / out-of-scope. Confirm with user when unclear.
Step 3: Fix
- Work in the PR branch worktree (same rules as
start-ticket). - Implement fixes; run quality gates when available.
- Commit with explicit staging; push.
Step 4: Respond
- Reply on review threads or add PR comment summarizing changes.
- Re-request review if appropriate.
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.