メニュー
Use when the user asks to add a comment to an existing roborev code review and close it without changing code.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Standalone Speedrift-native planning and Workgraph compilation. PlanForge V2 uses a model-mediated planner persona, validated schema, critic pass, and Speedrift module/model assignment to produce an executable Workgraph with tests, evals, drift gates, and fix loops. Use directly when you need discovery, decomposition, or an end-to-end Speedrift execution graph.
Use when agents need Google Workspace access across Drive, Docs, Sheets, Calendar, Slides, Tasks, People, or related GWS services; choose the correct gws-account profile before using gws CLI or domain-specific gws-* skills. Do not use Python gspread/googleapiclient or custom OAuth. Use msgvault for email search/reading.
gws CLI shared reference. Use before any gws-* skill to choose the correct gws-account profile, avoid raw gws config drift, and apply shared Drive flags, auth checks, output formatting, and security rules.
Use when a local Pi agent needs administrator privileges, a password-protected command, or approval for global or ambiguous deletion
Workgraph-first drift-control autopilot (driftdriver + coredrift + optional specdrift/datadrift/depsdrift/uxdrift/therapydrift/yagnidrift/redrift) with optional Amplifier runtime integration. Use for start/resume, dependency-aware execution, and keeping code/spec/intent synced without hard blocks.
Use when managing projects, programs, initiatives, dependencies, schedules, Workboard/PAIA Program tasks, Linear/GitHub/Google/Folio work, cross-system planning, weekly operating reviews, stale work rescue, operational task decomposition, or research-backed planning for Braydon's work. Covers a model-mediated program panel, research/evidence discovery, model-authored records, HTML inspection packets, change plans, approval gates, and execution ledgers.
| name | roborev-respond |
| description | Use when the user asks to add a comment to an existing roborev code review and close it without changing code. |
Record a comment on a roborev code review and close it.
Roborev reviews are normally created by the repository post-commit hook. Use this skill only to record a response on an existing review job and update its closed state.
$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.
If a message is provided, immediately execute:
roborev comment --job <job_id> "<message>" && roborev close <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