Agent Skills

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

roborev skills install

Available Skills¶

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.

Refine a branch¶

/roborev-refine runs an iterative review-fix-review loop on your branch. It finds failed reviews, fixes them, waits for re-review, and repeats until everything passes or the iteration limit is reached:

/roborev-refine
/roborev-refine --max-iterations 5
/roborev-refine --since HEAD~3
/roborev-refine --branch feature-xyz

Unlike roborev refine on the CLI, the skill performs the full workflow inside your agent session: it reviews via the daemon, fixes findings inline, commits, and re-reviews. This gives the agent direct access to the codebase while fixing, which can produce better results than the CLI's isolated worktree approach.

Agent-Specific Syntax¶

Checking Skill Status¶

See which skills are installed and whether any need updating:

roborev skills

The output shows each skill with per-agent status. Skills are checked for both Claude Code and Codex (if installed):

Skills:

  roborev-fix
  Discover and fix all open review findings in one pass

    Claude Code (installed)     /roborev-fix
    Codex (not installed)       $roborev-fix

Status values: installed, outdated, not installed, no agent (binary not found).

Updating Skills¶

Skills are updated automatically when you run:

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.

Plugin Distribution¶

Starting in 0.56, the roborev repository also ships agent plugin manifests that point at the same skill trees:

• .claude-plugin/plugin.json and .claude-plugin/marketplace.json for the Claude Code plugin marketplace.
• .codex-plugin/plugin.json for the Codex plugin system.

These let you install roborev skills through each agent's native plugin channel as an alternative to roborev skills install. The skill content is identical; the difference is who manages updates: roborev skills install is updated when you run roborev update, while plugin-managed installs follow each agent's plugin lifecycle.

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:

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. The /roborev-refine skill goes further, running an iterative loop that re-reviews after each fix until everything passes.

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¶

• Auto-Fix Agentic Loop with Refine: Automated fix loop
• Commands Reference: Full command list