Finishing a Development Branch

Automated PR preparation runs your project's test suite, formatters, linters, and type checkers across Node/JS, Rust, Python, and Go to catch issues before submission. This validates code quality, prevents CI failures, and eliminates manual pre-PR checks.

Yes. After completing feature work, you can automatically push your branch, create a PR with formatted summary and test plan, then monitor CI status to ensure the build passes before merging.

The process works across Node/JS, Rust, Python, and Go by executing their standard test commands (npm test, cargo test, pytest, go test) and running language-specific formatters, linters, and type checkers.

CI verification monitors your PR branch status and guides you through debugging and fixing failures, even when they're not directly caused by your code changes, ensuring the PR passes checks before merge.

Yes. A code reviewer subagent performs an objective self-review of your changes before the PR is submitted, helping catch issues and improve quality independently.

Code quality checks include running project tests, applying formatters and linters, performing type checking, and validating CI readiness—all automated to ensure standards are met before PR submission.