roborev-fix

Apply code patches to fix open review findings and close reviews.

1.6k|143|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/kenn-io/roborev --skill roborev-fix-kenn-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roborev-fix
Source: https://github.com/kenn-io/roborev/tree/main/internal/skills/claude/roborev-fix
Command: npx skills add https://github.com/kenn-io/roborev --skill roborev-fix-kenn-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixes all open review findings across specified jobs by applying fixes and closing reviews in one pass.

Core Features & Use Cases

  • Automatic collection of open reviews for provided job IDs and synthesis panels.
  • Unified fixes across multiple findings, followed by local validation and tests.
  • Closure workflow: post a summary comment for each fixed finding and close the original reviews, coordinating with panel reviews if present.

Quick Start

Invoke /roborev-fix [job_id...] to fix open reviews and close them.

Frequently Asked Questions about roborev-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically apply fixes and close open code reviews in one pass?

You can automatically fix open code reviews by invoking the command with specific job IDs. It orchestrates fetching open reviews, applying patches, running tests, and posting closure comments to resolve pending findings across multiple commits.

Can I resolve pending review findings across multiple commits at once?

Yes, you can resolve pending review findings across multiple commits by passing the job IDs. The tool collects open reviews, synthesizes unified fixes, validates them locally, and closes the original reviews with summary comments.

How does automated review management handle local validation before closing reviews?

Automated review management handles local validation by running tests immediately after applying unified code changes. This ensures the patches resolve the findings correctly before posting closure comments and closing the original reviews.

Do I need specific job IDs to start fixing open reviews?

Yes, you need specific job IDs to start fixing open reviews. The command requires you to explicitly provide job identifiers so it can automatically collect the corresponding open reviews, apply fixes, and execute the closure workflow.

What is the best way to fix open review findings and post closure comments automatically?

The best way to fix open review findings automatically is to use a CLI tool that orchestrates the entire workflow. It fetches the reviews, applies patches, runs tests, and posts a summary comment for each fixed finding before closing them.