synthesis-preflight

Assess six branch readiness dimensions and block PR creation on any failure.

15|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/synthesisengineering/synthesis-skills --skill synthesis-preflight-synthesisengineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: synthesis-preflight
Source: https://github.com/synthesisengineering/synthesis-skills/tree/main/synthesis-preflight
Command: npx skills add https://github.com/synthesisengineering/synthesis-skills --skill synthesis-preflight-synthesisengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires synthesis-code-audit.

What problem does it solve?

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?

Core Features & Use Cases

  • Six orthogonal dimensions: Branch Verification, Clean Working Tree, Test & Type Verification, Code Audit, Temporary Considerations, and Commit History, each graded as Pass, Warning, or Fail.
  • Mechanical verdict: A single Fail blocks PR creation; Warnings are surfaced for awareness.
  • Use Case: Teams validate branch readiness before PRs in CI/workflows, reducing late-stage defects and feedback loops.

Quick Start

Run preflight on your feature branch to verify readiness for PR.

Frequently Asked Questions about synthesis-preflight

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify branch readiness before creating a pull request?▼

Branch readiness before a pull request is verified by running a preflight check across six dimensions: branch verification, working tree cleanliness, test and type checks, code audit, temporary considerations, and commit history. Any single FAIL blocks PR creation while warnings surface concerns.

What is a mechanical go/no-go gate for branch merging?▼

A mechanical go/no-go gate for branch merging enforces an automated readiness verdict before PR creation. It checks six independent dimensions including test verification and commit history, where any FAIL blocks the pull request while warnings inform potential concerns.

Does preflight check if my code is correct before merging?▼

Preflight does not evaluate code correctness; it assesses mechanical branch readiness for PR creation. Code correctness is handled by self-review and code audit tools, while preflight enforces a go/no-go verdict on branch verification, tests, and commit history.

How do I run a pre-PR workflow check on my feature branch?▼

To run a pre-PR workflow check on a feature branch, execute a preflight gate to assess branch verification, clean working tree, test and type verification, and commit history. The six dimensions must pass for the branch to be mechanically ready for PR creation.

What dimensions are evaluated in a CI quality gate for pull requests?▼

A CI quality gate for pull requests evaluates six independent dimensions: branch verification, clean working tree, test and type verification, code audit, temporary considerations, and commit history. Each is graded as Pass, Warning, or Fail to determine readiness.

Can warnings in a branch readiness gate block PR creation?▼

Warnings in a branch readiness gate do not block PR creation; only a FAIL blocks it. Warnings are surfaced to inform potential concerns across dimensions like commit history or temporary considerations, while a single FAIL stops the pull request from being created.