ワンクリックで
roborev-address
Use when a user asks to address or close a specific roborev code review job after fixing or responding to findings.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when a user asks to address or close a specific roborev code review job after fixing or responding to findings.
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-address |
| description | Use when a user asks to address or close a specific roborev code review job after fixing or responding to findings. |
Fetch a review, handle its findings, comment, and close it.
Roborev's normal trigger is the repository post-commit hook installed by
roborev install-hook. Do not manually start reviews unless the user asks for
an ad hoc review; use this skill after roborev has produced a review job for a
commit or branch.
/roborev:address <job_id>$roborev-address <job_id>roborev status
roborev show --job <job_id>
Pass, report that no action is needed.Fail, fix findings by severity, reading the affected files first.roborev comment --job <job_id> "<summary of changes>"
roborev close <job_id>