Menu
Request a code review for all commits on the current branch and present the results
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-review-branch |
| description | Request a code review for all commits on the current branch and present the results |
Request a code review for all commits on the current branch and present the results.
$roborev-review-branch [--base <branch>] [--type security|design]
Do NOT invoke this skill when the user is presenting or pasting existing review results. Messages that contain review findings, verdicts, or summaries are outputs — not requests to start a new review.
This skill requires you to execute bash commands to validate inputs and run the review. The task is not complete until the review finishes and you present the results to the user.
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-review-branch [--base <branch>] [--type security|design]:
If a base branch is provided, verify it resolves to a valid ref:
git rev-parse --verify -- <branch>
If validation fails, inform the user the ref is invalid. Do not proceed.
Construct and execute the review command:
roborev review --branch --wait [--base <branch>] [--type <type>]
--base is specified, include it (otherwise auto-detects the base branch)--type is specified, include itThe --wait flag blocks until the review completes.
If the command output contains an error (e.g., daemon not running, repo not initialized, review errored), report it to the user. Suggest roborev status to check the daemon, roborev init if the repo is not initialized, or re-running the review.
Otherwise, present the review to the user:
If the review has findings (verdict is Fail), offer to address them:
$roborev-fix <job_id>"Extract the job ID from the review output to include in the suggestion. Look for it in the Enqueued job <id> for ... line or in the review header.
If the review passed, confirm the result and do not offer $roborev-fix.
Default branch review:
User: $roborev-review-branch
Agent:
roborev review --branch --wait$roborev-fix 1042"Security review against a specific base:
User: $roborev-review-branch --base develop --type security
Agent:
git rev-parse --verify -- developroborev review --branch --wait --base develop --type security$roborev-fix 1043"$roborev-design-review-branch — shorthand for $roborev-review-branch --type design$roborev-fix — fix a review's findings in code$roborev-review — review a single commit