Use only when the user explicitly invokes /roborev-respond
74%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./internal/skills/claude/roborev-respond/SKILL.mdRecord a comment on a roborev code review and close it.
/roborev-respond <job_id> [message]Invocation must be explicit: literal personal /roborev-respond, or structured
Claude Code skill selection.
Requests such as “respond to this review” without one of these explicit mechanisms must use
native behavior and must not run roborev.
roborev uses a local daemon. If a command fails with permission denied, the sandbox may be
blocking access to its loopback port or Unix socket. Retry the same Bash command with
dangerouslyDisableSandbox: true. Do not start or restart the daemon because a
sandboxed status probe cannot reach it.
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 daemon 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 job show --from-skill --job <job_id> --jsonIf 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 job comment --from-skill --job <resolved_job_id> "<message>" && roborev job close --from-skill <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 job show.
With message provided:
User: /roborev-respond 1019 Fixed all issues
Agent action:
roborev job comment --from-skill --job 1019 "Fixed all issues" && roborev job close --from-skill 1019Then 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 job comment --from-skill --job 1019 "The null check was a false positive" && roborev job close --from-skill 1019Then confirm: "Comment recorded and review #1019 closed."
/roborev-fix — fix a review's findings in code, then comment and close itkenn-io/roborev
5591632
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.