finishing-a-development-branch

Branch readiness validation enforces three-tier checks: Tier 1 runs automated tests, Tier 2 analyzes code quality and MCP patterns, and Tier 3 verifies integration prerequisites. A readiness score (0.00–1.00) summarizes all checks to guide merge decisions.

MCP pattern analysis compares your branch against historical merges to identify integration risk. This assessment feeds into the overall readiness score and helps determine whether a branch should merge, stay open as a PR, remain unpublished, or be discarded.

Serena risk telemetry provides integration risk metrics that inform the three-tier validation and readiness scoring. These metrics, combined with test results and code quality analysis, establish quantitative gate thresholds to determine merge safety.

Yes. The Skill integrates with CI pipelines to enforce Tier 1 test execution, Tier 2 code quality checks, and Tier 3 integration validation. Results feed directly into merge gate decisions and readiness scoring within your workflow.

Failed checks lower your readiness score, indicating merge risk. The Skill presents four options: merge anyway, open as a PR for review, keep the branch unpublished, or discard it. Lower scores signal which tiers need attention before proceeding.

The Skill requires automated tests to execute Tier 1 validation and integration checks to run Tier 3 assessment. Your CI system must support test execution and code quality analysis; the Skill orchestrates these within its three-tier framework.