PREFLIGHT

Check branch readiness before you open a PR

Preflight runs locally on your machine, scores your branch readiness, flags blockers and test gaps, and maps blast radius — all before a pull request exists.

Focus

Catch problems before review starts.

Model

Analysis locked to branch state.

Surface

CLI and local web dashboard.

Distribution

One install, public releases on GitHub.

Branch readiness

See your readiness score, blockers, and blast radius in one place

Understand the full impact of your changes before anyone else needs to look at them.

Preflight local dashboard showing branch readiness score, code findings, test quality, and active task queue.

Why before the PR

Catch blockers while the code is still yours to fix

As development velocity increases, waiting for PR review to catch quality issues adds delay and rework. Preflight moves the quality check earlier — to your local branch, while context is fresh and changes are easy to adjust.

Without Preflight

  • PR review is the first quality check
  • Issues found days after the code was written
  • Reviewers spend time on problems the author could have caught

With Preflight

  • Quality verified locally before the PR is opened
  • Blockers and test gaps surface while context is fresh
  • Reviews focus on architecture, intent, and system impact

Capabilities

What Preflight checks on your branch

Readiness scoring

Get a clear verdict — ready, needs review, or hold — with specific blockers listed.

Blast radius

Understand which parts of the codebase are affected by your changes, including downstream callers and dependencies.

Missing test detection

Identify changed exports and entrypoints that lack test coverage before they reach review.

Scope creep alerts

Detect unrelated changes that crept into your branch, so PRs stay focused on their stated intent.

AI code review

Get code review findings scoped to your current branch state. Results are invalidated when the branch changes.

Local-only execution

All analysis runs locally. No data leaves your machine, no accounts required, no telemetry.

Why teams use it

Surface issues while context is fresh

Blockers and test gaps are identified while the code is still in your editor, so fixes happen immediately instead of after review.

Reduce review cycles and rework

PRs arrive cleaner, so reviewers can focus on architecture and intent instead of catching preventable issues.

One install, no accounts required

One install command. Runs against any git repository immediately, with no configuration needed.

Install Linux, macOS, Windows

Unix shell

curl -fsSL https://raw.githubusercontent.com/octokraft/preflight-releases/main/scripts/install.sh | sh

PowerShell

irm https://raw.githubusercontent.com/octokraft/preflight-releases/main/scripts/install.ps1 | iex

Public repo

Install scripts, docs, release notes, and checksums. Source stays private.

FAQ

Common questions.

Does this replace PR review tools?

No. It makes PRs cleaner so review can focus on what matters.

What platforms are supported?

Linux/amd64 today, with more targets shipping as coverage expands.

Does it send code to the cloud?

Nothing leaves your machine. All analysis runs locally against your repo.

How do updates work?

Rerun the install script. Checksums and release notes are in the public repo.

Ship clean code. Skip the review ping-pong.

One command to install. Runs on every branch, every commit.