branch-review

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.

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.

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.

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.

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.

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.