synthesis-preflight

Assess git branch readiness with six checks and a go/no-go verdict.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a mechanical branch readiness gate so developers and CI pipelines can determine whether a feature branch is ready to become a pull request by surfacing blocking issues and non-blocking warnings.

Core Features & Use Cases

  • Six orthogonal checks: branch verification, clean working tree, tests & types, code audit, temporary considerations, and commit history, each graded pass/warning/fail.
  • Deterministic verdict: a single FAIL in any dimension produces NOT READY; all-pass yields READY, with warnings listed for awareness.
  • Integration scenarios: run locally before creating a PR, embed in CI pipelines as a pre-merge gate, or include in developer tooling to catch mechanical issues early.
  • Temporary considerations pattern: tracks and verifies resolution criteria for time-limited workarounds so resolved items are auto-removed from tracking.

Quick Start

Run preflight on the current branch and return a PASS/WARNING/FAIL report across branch verification, clean tree, tests & types, code audit, temporary considerations, and commit history.

Frequently Asked Questions about synthesis-preflight

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

FAQPage Schema
How do I check if a git branch is ready for a pull request?

To check if a git branch is ready for a pull request, use a mechanical preflight gate to run six orthogonal checks across branch verification, clean tree, tests, code audit, temporary considerations, and commit history. A single FAIL yields NOT READY; all-pass yields READY.

What is a mechanical pre-merge gate for CI pipelines?

A mechanical pre-merge gate for CI pipelines is an automated readiness check that grades branch verification, tests, code audit, and commit history as pass/warning/fail. It outputs a deterministic READY or NOT READY verdict to block merges when blocking issues are surfaced.

Can I use preflight checks to track temporary considerations in my code?

Yes, preflight checks can track temporary considerations by verifying resolution criteria for time-limited workarounds. Once resolved items meet the tracking criteria, they are automatically removed from the branch audit report.

How do I automate commit history audits before merging a feature branch?

Automate commit history audits before merging by embedding a preflight gate into CI pipelines or developer tooling. This evaluates commit history as one of six orthogonal checks, grading it pass/warning/fail to produce a deterministic branch readiness verdict.

What do I need to run branch readiness checks and code audits?

To run branch readiness checks and code audits, you need repository access plus test and type tooling configured in your environment. The preflight process requires these dependencies to execute its six orthogonal checks and return a valid go/no-go verdict.

Does a warning in a pre-merge check block the pull request?

A warning in a pre-merge check does not block the pull request. The preflight gate produces a NOT READY verdict only when a check receives a FAIL grade; warnings are listed for awareness while an all-pass yields READY.