roborev

Automate code review management with a daemon and CLI.

Updated May 9, 2020

Search Tags:#automation #cli #claude-code #code-review #pre-push #daemon

Ready to run

npx skills add https://github.com/Fenntasy/dotfiles --skill roborev-fenntasy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: roborev
Source: https://github.com/Fenntasy/dotfiles/tree/main/claude/skills/roborev
Command: npx skills add https://github.com/Fenntasy/dotfiles --skill roborev-fenntasy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated code review management with roborev daemon and CLI. Covers claude-code reviews, fixing findings, pre-push workflow, daemon management, per-project config. Use when: checking reviews, fixing findings, managing review status, or before pushing.

Core Features & Use Cases

Daemon-based automated code reviews triggered by post-commit hooks using claude-code.
CLI commands to inspect, fix, and iterate on findings, with per-project configuration.
Enforces pre-push workflows and supports per-repo config for teams.

Quick Start

Install roborev, configure your first project, and start the daemon to begin automated reviews.

Frequently Asked Questions about roborev

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

FAQPage Schema

How do I automate code review workflows using Claude-code?▼

Automated code review workflows using Claude-code are triggered by a daemon that runs post-commit hooks. This setup provides continuous review feedback and manages iterative finding resolution for software projects.

Can I enforce a pre-push gatekeeping check for code findings?▼

Pre-push gatekeeping is enforced by the CLI to prevent pushing code with unresolved findings. You inspect, fix, and iterate on findings locally before the workflow permits a push to the remote repository.

How do I configure per-project settings for automated code reviews?▼

Per-project configuration allows teams to define specific automated review rules and settings for each repository. You configure these settings locally to tailor the daemon and CLI behavior to your project's needs.

What is the best way to manage and resolve iterative code review findings?▼

Resolving iterative code review findings is managed through CLI commands that let you inspect, fix, and update review statuses. The daemon continuously applies checks while you iterate until all findings are cleared.

Does this automated code review daemon work without external dependencies?▼

The automated code review daemon operates without external dependencies. It integrates directly with Claude-code and your local git hooks to manage review workflows and per-project configurations independently.

When do I need a daemon-based approach for continuous code review?▼

A daemon-based approach for continuous code review is needed when teams require automated feedback triggered by post-commit hooks. It supports ongoing review management, pre-push enforcement, and iterative finding resolution.