Skip to content
cccskills
FreePublished on GitHub

roborev-respond

Add a comment to a roborev code review and close it

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

roborev-respond

Record a comment on a roborev code review and close it.

Usage

/roborev-respond <job_id> [message]

IMPORTANT

This skill requires you to execute bash commands to record the comment and close the review. The task is not complete until you run both commands and see confirmation output.

These instructions are guidelines, not a rigid script. Use the conversation context. Skip steps that are already satisfied. Defer to project-level CLAUDE.md instructions when they conflict with these steps.

Instructions

When the user invokes /roborev-respond <job_id> [message]:

1. Validate input

If no job_id is provided, inform the user that a job ID is required. Suggest roborev status or roborev fix --list to find job IDs. Discovery surfaces synthesis parents (and non-panel reviews), never individual panel members, so the job ID you comment on and close is the parent.

If a job_id is provided, inspect it before closing:

roborev show --job <job_id> --json

If job.panel_role is "member", do not comment on or close that job. Resolve the synthesis parent for the same job.panel_run_uuid if it is already known from the conversation or discovery output; otherwise ask the user for the synthesis parent ID. Only continue once the resolved job ID is a synthesis parent or a non-panel review.

2. Record the comment and close the review

If a message is provided, immediately execute:

roborev comment --job <resolved_job_id> "<message>" && roborev close <resolved_job_id>

If the message contains quotes or special characters, escape them properly in the bash command.

If no message is provided, ask the user what they'd like to say, then execute the commands with their comment.

3. Verify success

Both commands will output confirmation. If either fails, report the error to the user. Common causes:

  • The daemon is not running
  • The job ID does not exist
  • The repo is not initialized (suggest roborev init)
  • The review is already closed (not an error, but worth noting to the user)

The comment is recorded in roborev's database and the review is closed. View results with roborev show.

Examples

With message provided:

User: /roborev-respond 1019 Fixed all issues

Agent action:

roborev comment --job 1019 "Fixed all issues" && roborev close 1019

Then confirm: "Comment recorded and review #1019 closed."


Without message:

User: /roborev-respond 1019

Agent: "What would you like to say about review #1019?"

User: "The null check was a false positive"

Agent action:

roborev comment --job 1019 "The null check was a false positive" && roborev close 1019

Then confirm: "Comment recorded and review #1019 closed."

See also

  • /roborev-fix — fix a review's findings in code, then comment and close it

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Allows you to view the user's screen as well as several hours of history. Use when the user makes a reference to their recent work, for which it'd be helpful to see the screen. This skill MUST be used whenever you need to resolve ambiguity in a user request, where the user hasn't specified enough context to do the task. Examples include disambiguating the specific user/app/document/error the user is referring to. You must also use this skill if the user asks about any question regarding Chronicle or asks what you can see from the screen.

The English summary is being prepared. Showing the original description.

obra/dotfiles116Updated Oct 13, 2026

Use when verifying a running application end-to-end through its real interface — a web UI, a CLI, or a TUI — by writing and executing agent-run "scenario cards" against a freshly built instance with falsifiable assertions. Trigger on "test it end to end", "prove the UI actually works", "write/run a scenario", or after a change touches a user-facing surface that unit tests can't fully cover. Not for unit tests, pure code review, or API-only checks.

The English summary is being prepared. Showing the original description.

obra/dotfiles116Updated Oct 13, 2026

Use when documentation needs creating, checking, or maintaining — docs may have drifted from code, pre-release doc verification, updating docs after finishing code work, adding or enforcing project terminology, deciding where a new doc should live, or a routine re-audit of previously verified docs.

The English summary is being prepared. Showing the original description.

obra/dotfiles116Updated Oct 13, 2026

Use MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context with pre-loaded MCP integrations

The English summary is being prepared. Showing the original description.

obra/dotfiles116Updated Oct 13, 2026

Request a design review for a commit and present the results

The English summary is being prepared. Showing the original description.

obra/dotfiles116Updated Oct 13, 2026

Request a design review for all commits on the current branch and present the results

The English summary is being prepared. Showing the original description.

obra/dotfiles116Updated Oct 13, 2026

See all skills by obra

Report a problem with this skill