tomevault-io roborev-review
Request a code review for a commit and present the results.
Usage
/roborev-review [commit] [--type security|design]
When NOT to invoke this skill
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.
IMPORTANT
This skill requires you to execute bash commands to validate the commit and launch the review. The task is not complete until the background 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.
Instructions
When the user invokes /roborev-review [commit] [--type security|design]:
1. Validate inputs
If a commit ref is provided, verify it resolves to a valid commit:
git rev-parse --verify -- <commit>^{commit}
If validation fails, inform the user the ref is invalid. Do not proceed.
2. Build the command
Construct the review command:
roborev review [commit] --wait [--type <type>]
- If no commit is specified, omit it (defaults to HEAD)
- If
--typeis specified, include it
3. Run the review in the background
Launch a background task that runs the command. This lets the user continue working while the review runs.
Use the Task tool with run_in_background: true and subagent_type: "Bash":
roborev review [commit] --wait [--type <type>]
Tell the user that the review has been submitted and they can continue working. You will present the results when the review completes.
4. Present the results
When the background task completes, read the output.
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:
- Show the verdict prominently (Pass or Fail)
- If there are findings, list them grouped by severity with file paths and line numbers so the user can navigate directly
- If the review passed, a brief confirmation is sufficient
5. Offer next steps
If the review has findings (verdict is Fail), offer to address them:
- "Would you like me to fix these findings? You can run
/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.
Examples
Default review of HEAD:
User: /roborev-review
Agent:
- Launches background task:
roborev review --wait - Tells user: "Review submitted for HEAD. I'll present the results when it completes."
- When complete, presents the verdict and findings grouped by severity
- If findings exist: "Would you like me to fix these findings? Run
/roborev-fix 1042" - If passed: "Review passed with no findings."
Security review of a specific commit:
User: /roborev-review abc123 --type security
Agent:
- Validates
abc123resolves to a valid commit - Launches background task:
roborev review abc123 --wait --type security - Tells user: "Security review submitted for abc123. I'll present the results when it completes."
- When complete, presents the verdict and findings
- If findings exist: "Would you like me to fix these findings? Run
/roborev-fix 1043"
See also
/roborev-design-review— shorthand for/roborev-review --type design/roborev-fix— fix a review's findings in code/roborev-review-branch— review all commits on the current branch
Converted and distributed by TomeVault — claim your Tome and manage your conversions.