respond-to-review
Skill904 starsChanged 5 days agoMITView on GitHub
Address pull request review feedback, make focused changes, and summarize the outcome in one short reply. Use when the user asks to handle, address, or respond to review comments. Not for requesting or performing a code review.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- chrislacey89/skillstheir own version, first seen Nov 1, 2026
- dativo-io/talontheir own version, first seen Oct 25, 2026
- mojopoly/three-loopstheir own version, first seen Oct 20, 2026
- eloqdata/eloqkvtheir own version, first seen Oct 8, 2026
- SteveVitali/agent-discoursetheir own version, first seen Aug 20, 2026
- igmarin/elixir-phoenix-skillstheir own version, first seen Jul 21, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- eloqdata/eloqkv★ 1.5ksame name
- dativo-io/talon★ 18same name
- chrislacey89/skills★ 7same name
- igmarin/elixir-phoenix-skills★ 4same name
- mojopoly/three-loops★ 0same name
- SteveVitali/agent-discourse★ 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 repository18 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- ios/CLAUDE.mdCLAUDE.md
- rome_apps/CLAUDE.mdCLAUDE.md
- add-oauth-integrationSkill
- babysit-prSkill
- color-auditSkill
- dddSkill
- file-issueSkill
- imports-ofSkill
- loop-northstarSkill
- loop-reconcileSkill
- move-codeSkill
- release-rome-imageSkill
- secondary-text-auditSkill
- todos-to-github-projectSkill
- ux-semantics-auditSkill
- validate-oauth-integrationSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
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 11
Leave nothing open: Every finding ends fixed here, fixed in a blocking PR, filed as an issue, or declined with a reason.
- Distinctive: line 14
When the issue the PR closes looks wrong, ask the user.
“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
Respond to review feedback
The goal is to get the PR merged as the change it set out to be, with every reviewer concern settled. Two things defeat that: the PR grows with each review round and drifts from its scope, or findings stay open and the next round raises them again.
- Stay on scope. Fix real defects this PR introduced, each proven by a test that fails without the fix. A defect in prose, including a PR description that misstates the change, has no test: correct it directly and say so in the reply. An existing defect that makes this PR wrong or unsafe to merge — the change depends on it, or makes it reachable — gets its own PR on a branch off the base branch, and this PR's description names it in a Blocked by line. Open that PR from a new session when the environment allows, and take its number from that session's report; otherwise open it from this session. Everything else stays out of this PR; file a bug issue for a real defect unless one already exists.
- Leave nothing open. Every finding ends fixed here, fixed in a blocking PR, filed as an issue, or declined with a reason.
- Close the loop in one short reply. Say what changed, what did not, and why, so the reviewer can approve without asking again.
When the issue the PR closes looks wrong, ask the user. Never edit the issue.
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.

