is-it-ready
CLI + VSCode extension for release confidence checks

is-it-ready is a CLI (with a VS Code extension) that answers one question before every push: is my code actually ready to go to main?
It started from workflow friction. Some engineers on my team were adamant that git pre-commit hooks was necessary to run linting and formatting checks, but that slows down commits and creates an unnecessary coupling. I've always personally just run the checks I needed to throughout development, though at the same time, I occasionally forgot to run one of the required tasks locally and only found out in CI.
The real issue wasn’t tooling - it was feedback timing.
So I built a config-driven readiness gate that mirrors CI locally. One command runs formatting, linting, tests, audits, or any custom task - in parallel - and produces a deterministic pass/fail signal.
Key design decisions:
- Exit codes are the source of truth (CI-aligned).
- Tasks are fully command-driven, making it ecosystem-agnostic (I use it for Node and Python projects).
- Parallel execution for speed, with controlled output.
- Optional, user-defined
--fixmode for safe, explicit auto-fixes. - Watch mode debounced to avoid thrashing.
The only requirement is a config file, which makes adoption trivial - even on repositories that don't explicitly support is-it-ready.
This project reflects how I think about engineering: improve feedback loops, reduce friction, and make the "right thing" the easiest thing to do.