A wrong Node or Python version, stopped Redis container, or missing .env key can waste hours disguised as an application bug. I wanted one sub-3-second check against what the repo actually asks for.
Check the machine against the repository manifests.
TypeScript shares the checking engine across the CLI (@envpreflight/cli), MCP server (@envpreflight/mcp), VS Code extension, and composite GitHub Action.
Runs locally with zero network calls and zero telemetry. .env and .env.example files are parsed for variable key names only; secret values are never read, printed, or logged.
Readiness checks verify versions, port reachability, and key presence; they do not validate database schemas or test live third-party API credentials.
I kept losing hours debugging cryptic application crashes that turned out to be a stopped Docker container, a wrong Node version, or a missing .env variable.
Checking setup requirements across README files and config manifests by hand is tedious, and most tools only fail after the build is already broken.
envpreflight reads your repository's manifests and checks local runtimes, database ports, Docker status, and missing .env keys in under three seconds.
Run one command before you start coding, or let your AI agent run it first, to get a clear checklist of what is missing and the exact command to fix it.