agentleFS
rome-osrome-os/rome/.claude/skills/respond-to-review/SKILL.md

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

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
  1. Distinctive:

    Leave nothing open: Every finding ends fixed here, fixed in a blocking PR, filed as an issue, or declined with a reason.

    line 11
  2. Distinctive:

    When the issue the PR closes looks wrong, ask the user.

    line 14

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.