gastrobrain-code-review

You can automate pre-merge code reviews by running a systematic seven-checkpoint process that executes flutter analyze and flutter test, checks git status, and generates explicit pass/warn/fail outputs with merge instructions upon approval.

A checkpoint-based code review enforces a repeatable governance framework across seven stages, validating branch status, roadmap alignment, acceptance criteria, technical standards, localization, and merge readiness before allowing a feature branch to merge.

Merge instructions are generated automatically after your feature branch passes the required quality gates, including automated analysis and test execution, yielding an explicit approval status and step-by-step readiness assessment for the develop merge.

Yes, the pre-merge review process explicitly checks localization considerations and acceptance criteria as part of its context-aware review, ensuring full technical standard compliance and feature completeness before generating merge readiness outputs.

Yes, this code review framework operates without external dependencies, applying its seven-checkpoint governance directly to your git status, automated test results, and branch context to produce remediation guidance and merge instructions.

Feature branches fail pre-merge quality gates when automated analysis or test execution detects issues, triggering a fail status with clear remediation guidance to fix technical standard violations before reattempting the develop merge.