synthesis-preflight
Synthesis Preflight
Preflight is a branch readiness gate. It does not evaluate whether your code is correct — that is the job of synthesis-implementation-integrity (self-review) and synthesis-code-audit (quality scan). Preflight asks a different question: is this branch mechanically ready to become a PR?
A branch can contain perfectly good code and still fail preflight: tests broken, uncommitted changes left behind, vague commit messages, a stale workaround that should have been removed. Preflight catches the things that fall between "the code works" and "the branch is ready."
Where This Fits
| Skill | Scope | When to use |
|---|---|---|
| implementation-integrity | Self-verification of a single implementation | After completing work — "Is my code genuinely complete?" |
| code-audit | 10-dimension quality scan of a diff | After implementation — systematic quality measurement |
| preflight (this one) | Branch readiness gate | Before creating a PR — "Is this branch ready?" |
The natural flow: Implement → self-verify (implementation-integrity) → quality scan (code-audit) → branch gate (preflight) → create PR → peer review (pr-review).
Preflight assumes implementation-integrity was already run during development. It does not re-check whether the code is complete — it checks whether the branch is ready to leave your machine.