القائمة
Add a comment to a roborev code review and close it
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user asks to fix open failing reviews, invokes /roborev-fix, or provides job IDs; do not use when the user only pastes review findings with no request to discover or close reviews
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.
Use when the user asks to fix open failing reviews, invokes $roborev-fix, or provides job IDs; do not use when the user only pastes review findings with no request to discover or close reviews
Request a design review for all commits on the current branch and present the results
Request a design review for a commit and present the results
Iterative review-fix loop for the current branch — reviews via daemon, fixes inline, re-reviews until passing or max iterations reached
| name | roborev-respond |
| description | Add a comment to a roborev code review and close it |
Record a comment on a roborev code review and close it.
/roborev-respond <job_id> [message]
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.
When the user invokes /roborev-respond <job_id> [message]:
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.
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.
Both commands will output confirmation. If either fails, report the error to the user. Common causes:
roborev init)The comment is recorded in roborev's database and the review is closed. View results with roborev show.
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."
/roborev-fix — fix a review's findings in code, then comment and close it