branch-review

Name: branch-review
Availability: InStock
Author: BenchFlow

Run linting, type checks, and tests on git branch diffs before pushing.

317|40|Updated Jan 21, 2025

Search Tags:#automation #git #testing #code review #linting #pre-push

Ready to run

npx skills add https://github.com/benchflow-ai/benchflow --skill branch-review-benchflow-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: branch-review
Source: https://github.com/benchflow-ai/benchflow/tree/main/.agents/skills/branch-review
Command: npx skills add https://github.com/benchflow-ai/benchflow --skill branch-review-benchflow-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the risk of pushing broken or unpolished code by automating a comprehensive pre-push sanity check that combines linting, type checking, testing, and multi-domain code reviews.

Core Features & Use Cases

Correctness Gates: Automatically runs ruff, type checking, and scoped unit tests to catch blockers before they reach the repository.
Intelligent Routing: Fans out reviews to specialized cleanup, test, and documentation agents based on the specific files changed in the branch.
Use Case: Before pushing a feature branch, run this skill to ensure your code passes all CI-equivalent gates and receives a multi-perspective review without needing to manually trigger separate audit tools.

Quick Start

Run the branch-review skill to perform a full pre-push sanity check and review on your current branch.

Frequently Asked Questions about branch-review

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

FAQPage Schema

How do I automate pre-push code review and linting for a git branch?▼

Automating pre-push code review involves running linting, type checking, and scoped unit tests on git branch diffs. This skill orchestrates ruff, pytest, and specialized review agents to catch blockers and provide cross-referenced feedback before code reaches the repository.

What is a pre-push sanity check and how does it prevent broken code commits?▼

A pre-push sanity check validates modified files by running correctness gates like ruff linting, type checking, and pytest. It prevents broken commits by identifying blockers across code, tests, and documentation before a git push operation executes.

Do I need ruff and pytest installed locally to run automated pre-push checks?▼

Yes, you need local access to ruff, pytest, and the benchflow agent registry. These dependencies are required to execute the validation gates and specialized review partitions that assess code quality on your branch diff.

Can I run multi-domain code reviews on modified files without triggering separate audit tools?▼

Yes, you can run multi-domain reviews by fanning out modified files to specialized cleanup, test, and documentation agents. This intelligent routing provides a multi-perspective review automatically, eliminating the need to manually trigger separate audit tools.

What's the best way to run CI-equivalent quality gates on a feature branch before pushing?▼

The best way to run CI-equivalent quality gates is to execute a full pre-push sanity check on your feature branch. This automatically orchestrates ruff, type checking, and scoped unit tests to ensure your code passes all validation before reaching the repository.

Why does automated branch review use specialized agents for tests and documentation?▼

Automated branch review uses specialized agents to provide targeted, cross-referenced feedback based on the specific files changed. Intelligent routing sends partitions to cleanup, test, and documentation agents, ensuring comprehensive multi-domain coverage that generic linting cannot achieve.