Skip to content
GitHub stars

Agent Skills

Install slash commands that let AI agents request reviews and fix findings directly:

Terminal window
roborev skills install

Available Skills

SkillDescription
/roborev:review [commit] [--type ...]Request a code review for a commit
/roborev:review-branch [--base ...] [--type ...]Review all commits on the current branch
/roborev:design-review [commit]Request a design review for a commit
/roborev:design-review-branch [--base ...]Design review all commits on the current branch
/roborev:fix [job_id...]Discover and fix all open review findings in one pass
/roborev:respond <job_id> [message]Add a response to document changes

Usage

Review a commit

Request a code review without leaving your agent session:

/roborev:review
/roborev:review abc123
/roborev:review --type security

The skill enqueues a review and waits for the result so it can present findings inline. If you already have reviews queued from the post-commit hook, use /roborev:fix to address them instead of requesting new ones.

Review a branch

Review all commits since the current branch diverged from main:

/roborev:review-branch
/roborev:review-branch --base develop
/roborev:review-branch --type security

The skill enqueues a branch review and waits for results so the agent can present them inline.

Design review

Request a design-focused review that evaluates completeness, feasibility, and task scoping:

/roborev:design-review
/roborev:design-review abc123

Enqueues a design review and waits for the result, following the same pattern as the other review skills.

Design review a branch

Review all commits on the current branch with a design-focused lens:

/roborev:design-review-branch
/roborev:design-review-branch --base develop

This is the branch equivalent of /roborev:design-review.

Fix all open reviews at once

The most powerful skill is /roborev:fix. With no arguments it discovers all open failed reviews on recent commits and fixes them in a single pass:

/roborev:fix

You can also target specific jobs:

/roborev:fix 1019 1021

The agent:

  1. Discovers open reviews (or uses provided job IDs)
  2. Fetches all reviews and collects findings
  3. Groups findings by file and prioritizes by severity
  4. Fixes all issues across all reviews
  5. Runs tests to verify
  6. Records a comment on each closed review
  7. Offers to commit

This is the interactive equivalent of roborev fix --batch — the agent sees all findings at once and can make coordinated fixes across related issues.

Fix a single review

Target a specific job ID with /roborev:fix:

/roborev:fix 1019

The agent fetches the review, fixes issues by priority, runs tests, and offers to commit.

Agent-Specific Syntax

AgentSyntax
Claude Code/roborev:review, /roborev:review-branch, /roborev:design-review, /roborev:design-review-branch, /roborev:fix, /roborev:respond
Codex$roborev:review, $roborev:review-branch, $roborev:design-review, $roborev:design-review-branch, $roborev:fix, $roborev:respond

Checking Skill Status

See which skills are installed and whether any need updating:

Terminal window
roborev skills

Updating Skills

Skills are updated automatically when you run:

Terminal window
roborev update

How It Works

Skills are installed as agent-specific configuration:

  • Claude Code: Custom slash commands in ~/.claude/
  • Codex: Custom agent skills directory

The review skills use --wait internally so the agent can present results inline. The fix skills call roborev show --job <id> --json to fetch review data, then parse and present findings to the agent in a structured format. All reviews (whether requested via skills or the post-commit hook) appear in the TUI queue.

Waiting for Hook-Triggered Reviews

When a post-commit hook already enqueues reviews, agents don’t need roborev review --wait (which would create a duplicate job). Use roborev wait instead:

Terminal window
git commit -m "Fix auth validation" # Hook triggers review
roborev wait --quiet # Block until verdict (exit 0=pass, 1=fail)

This is more token-efficient than polling roborev list or roborev show because the agent makes a single blocking call and reads the exit code. See Waiting for a Review Without Enqueuing for the full flag reference.

Skills vs Async Reviews

For most workflows, the async approach is better: reviews run automatically via the post-commit hook, results accumulate in the TUI, and you address them when ready. This keeps your agent session focused on writing code and creates a persistent record of what needs attention.

Skills are useful when you want to explicitly request a review during an agent session, for example to review uncommitted changes or to get a design review before committing. The /roborev:fix skill is valuable in any workflow because it pulls findings from the TUI queue and addresses them within your session.

For fully automated fixing outside an agent session, use roborev fix --batch (headless, no agent interaction) or roborev refine (iterative loop until all reviews pass).

See Also