New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Respond To Review

by rome-os in rome-os/rome

Address pull request review feedback, make focused changes, and summarize the outcome in one short reply.

MITAuto-check passedDevelopment

Install Respond To Review

skills CLI
$ npx skills add rome-os/rome --skill respond-to-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rome-os/rome respond-to-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rome-os/rome.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/respond-to-review .claude/skills/respond-to-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
respond-to-review
GitHub stars
743
Token cost
~1k tokens
SKILL.md length
628 words
Files
1
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Address pull request review feedback, make focused changes, and summarize the outcome in one short reply.

  • Works in 4 steps: Gather and dedupe → Classify every finding → Fix what earned a fix → …
  • The user asks to handle
  • SKILL.md covers Phase 1 — Gather and dedupe, Phase 2 — Classify every finding, Phase 3 — Fix what earned a fix and Phase 4 — Write one short…
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Respond To Review is an agent skill from rome-os/rome. 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.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: A compounding agent OS for recursive agents. Also an open source alternative to Grok Bot and Meta's Muse. The licence is MIT.

When your agent uses it

  • The user asks to handle
  • Respond to review comments

Example prompts

  • “/respond-to-review”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Gather and dedupe
  2. Classify every finding
  3. Fix what earned a fix
  4. Write one short summary reply

What it can do on your machine

Read from SKILL.md and the folder at commit ccf62e7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Respond To Review loads about 1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 628 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rome-os/rome at commit ccf62e7, republished under its MIT licence (© rome-os). 628 words, ~1,000 tokens.

Download SKILL.mdSave it as .claude/skills/respond-to-review/SKILL.md (or your agent's skills folder).
name
respond-to-review
description
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.

Respond to review feedback

Goal end-state: every finding on the PR has exactly one of four answers — a minimal fix with a test, a corrected claim in the PR description, a follow-up issue, or a written decline. The PR's diff grows as little as possible.

Classification precedes code. Never start implementing a finding before classifying it.

Phase 1 — Gather and dedupe

  1. Pull every review body and inline comment on the PR. Drop reviews marked "This review has been superseded."
  2. Merge duplicate findings — same file, same defect — into one item for classification.
  3. Discard the bots' severity labels and verdicts. Phase 2 re-derives priority.

Phase 2 — Classify every finding

Run each finding through these tests in order. The first test that matches decides the bucket.

Test 1 — the bot hedged

If the bot itself presents the finding as optional or non-blocking — "no action required", "consider", "worth noting": decline.

Test 2 — the PR already disclosed it

If the finding restates a "Not in this PR" item, a stated tradeoff, or a documented transitional state: decline, pointing at the section that covers it.

Test 3 — no caller can reach it

Ask what concrete caller, with what concrete input, hits the defect on main plus this diff. If the answer needs a future adapter, a third-party implementation, an input no caller produces, or a scale nothing is wired to reach: decline, stating what would have to exist first. If the concern matters later, record it as one sentence in the interface contract or as a follow-up issue.

Test 4 — the defect predates the diff

If the defect exists on main without this diff: follow-up issue, linked from the reply.

Exception: if the PR's own claims depend on the old code being correct — for example, a claim of parity with it — fix the defect in this PR.

Test 5 — code or claim

The finding is real, reachable, and introduced here. If it does not contradict a claim in the PR description, fix the code. If it does, trace the claim to the issue the PR closes:

  • The issue demands the claim: fix the code.
  • The claim is author-added, or there is no linked issue: fix the code or shrink the claim, whichever leaves the smaller diff.
  • The issue demands the claim and the requirement looks wrong: stop and ask the user. Never edit the issue.

Shrinking a claim means editing the PR description and stating the change in the reply.

Show full SKILL.md (221 more words)Show less

Phase 3 — Fix what earned a fix

For each finding in the fix bucket:

  1. Reproduce the finding as a failing test against real callers. If no such test can be written, return the finding to Phase 2 as a decline.
  2. Make the smallest change that passes. Prefer deleting or narrowing over adding. A defensive branch requires both a test that fails without it and a caller that can reach it.
  3. Check that reverting the fix fails exactly the new test.
  4. When the accumulated response diff nears a third of the PR's own diff, stop. Shrink a claim or move the rest to a follow-up issue.

Phase 4 — Write one short summary reply

Post exactly one short reply in the PR conversation thread after handling the review. Do not reply to individual comments or inline threads. Do not post cross-links or acknowledgments on each finding.

Summarize the fixes and validation, any corrected PR claims, and follow-up issues with links. Group declined findings by reason and mention only what the reviewer needs to understand the outcome. Keep the reply to a short paragraph or a few brief bullets. Do not enumerate findings one by one.

A "Not in this PR" line or a stated tradeoff in the PR description supports declining a finding. Write those sections before requesting review.

© rome-os, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/respond-to-review of rome-os/rome.

Open the folder on GitHubat commit ccf62e7

Compare with similar skills

Respond To Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Respond To Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Respond To Review this skillrome-os/rome743—~1kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    91k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from rome-os/rome

All 18 skills in this repo

  • Color Audit

    rome-os/rome

    Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…

    748 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • Secondary Text Audit

    rome-os/rome

    Audit the subordinate copy in a UI — section descriptions, field helper text, hints, card subtitles, empty-state body copy, tooltip bodies — against the secondary-text ruleset, and emit a per-string…

    748 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • UX Semantics Audit

    rome-os/rome

    Audit an existing UI/UX design (React/JSX/TSX components, HTML, or generated app code) against a tiered ruleset of verifiable UX principles, and produce structured, evidence-cited findings that a…

    748 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Add OAuth Integration

    rome-os/rome

    Add a new Rome-managed OAuth integration for a third-party service so a user can delegate access by clicking Connect, and Rome can act on the service with the delegated token (the GitHub/Slack model…

    748 GitHub stars~3.6k tokensUpdated today
    Auto-check passed

  • Composio CLI

    rome-os/rome

    Help users operate the published Composio CLI to find the right tool, connect accounts, inspect schemas, execute tools, subscribe to trigger events with composio listen, script workflows with…

    748 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

  • File Issue

    rome-os/rome

    File one GitHub issue from a description the user gives — classify it as a bug report, feature request, or task spec, gather what the body needs from the tracker and the code, ask the user only for…

    748 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Respond To Review

What does Respond To Review do?

Address pull request review feedback, make focused changes, and summarize the outcome in one short reply. Respond To Review is an agent skill from rome-os/rome. Address pull request review feedback, make focused changes, and summarize the outcome in one short reply.

When should I use Respond To Review?

Respond To Review fits situations like: the user asks to handle; respond to review comments.

How do I install Respond To Review in Claude Code?

Run `npx skills add rome-os/rome --skill respond-to-review -a claude-code`. Or copy the skill folder (.claude/skills/respond-to-review in rome-os/rome) into .claude/skills/respond-to-review in your project. Claude Code loads it when a task matches its description.

How do I install Respond To Review in Codex?

Run `npx skills add rome-os/rome --skill respond-to-review -a codex`. Or copy the skill folder (.claude/skills/respond-to-review in rome-os/rome) into .agents/skills/respond-to-review in your project. Codex loads it when a task matches its description.

Can I use Respond To Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rome-os/rome --skill respond-to-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/respond-to-review, .gemini/skills/respond-to-review, .github/skills/respond-to-review and .opencode/skills/respond-to-review in your project.

What does Respond To Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Respond To Review is instructions for the agent only.

Does Respond To Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Respond To Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Respond To Review use?

Respond To Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Respond To Review use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Respond To Review?

Skills that share tags, products or a category with Respond To Review: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 91k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Respond To Review?

rome-os (a GitHub organization) maintains it in rome-os/rome, which has 743 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 10, 2026.

Source: rome-os/rome on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.