Preflight
What exactly am I about to commit?
Preflight is a deterministic, read-only CLI that inspects the Git index immediately before git commit. It summarizes the staged snapshot and reports evidence-backed repository states developers commonly regret committing.
python -m pip install evo-preflight
preflight
Preflight inspects staged paths and blob sizes, common generated artifacts, tracked files matching .gitignore, foundational repository files, and the repository default branch. Every finding says what was observed, why it matters, and a suggested fix.
It never blocks a commit, changes repository state, runs tests or builds, scans secrets, certifies releases, installs hooks, uses AI, sends telemetry, or accesses the network.
Commands
preflight
preflight --json
preflight --largest
preflight --version
preflight explain large-staged-file
preflight --config preflight.toml
Findings always return exit code 0. Exit code 2 means the repository or configuration is unavailable; 3 means an unexpected internal error occurred.
What it reports
- staged files of at least 100 MB;
- staged snapshots of at least 500 MB, with largest contributors;
- Python caches:
__pycache__,*.pyc, and*.pyo; - virtual environments:
.venvandvenv; - build artifacts:
build,dist,*.whl, and*.egg-info; *.jsonland configured generated directories;- tracked files matching standard Git ignore rules;
- a missing root README, LICENSE, or
.gitignore; - a default branch named
master, reported without claiming it is wrong; - the ten largest tracked files when
--largestis requested.
Preflight reads staged content from Git, so unstaged edits are never described as part of the next commit.
Configuration
Preflight automatically reads preflight.toml from the repository root. Configuration is declarative, has no commands or scripting, and rejects unknown keys.
version = 1
[limits]
large_file_mb = 100
large_snapshot_mb = 500
[generated]
directories = ["benchmarks/results", "telemetry"]
Development
python -m pip install -e ".[dev]"
ruff check .
mypy
python -m unittest discover -s tests -v
python -m build
twine check dist/*
See CONTRIBUTING.md for the contribution workflow and CHANGELOG.md for release history.
Metadata
Release files for evo-preflight 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| evo_preflight-0.1.0.tar.gz | 17.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| evo_preflight-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.5 kB
Release files / evo_preflight-0.1.0.tar.gz
| Download URL | evo_preflight-0.1.0.tar.gz |
|---|---|
| Size | 17.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fce701748c0dd091525905f4d1e98a3b969df89e9472f0015483256535aef3c9
|
|
BLAKE2b-256 checksum How to use checksums |
1b5f14d96d7ecf5d584bb16a2b9505cb743d49735f8f5f8bb9eb7932c724ed15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency logRelease files / evo_preflight-0.1.0-py3-none-any.whl
| Download URL | evo_preflight-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b2837aaa34f0d1902cd5b238423aac486821243edc03b9de5ed8ad01f0378715
|
|
BLAKE2b-256 checksum How to use checksums |
ce14e76d3ecbf0c2f3926d5e2cddbba712fe7dca15a042570f9d6b8c0092578a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 5, 2026.
Transparency log