check-pr-readiness

Run a PR readiness check to validate your branch diff against a fixed base commit, executing typecheck, lint, format, and tests sequentially while stopping immediately on the first failure to reduce noise.

Yes, a residue sweep flags risky left-behind additions in changed source lines, including newly introduced console.log, .only, .skip, debugger statements, and TODO or FIXME markers before opening a pull request.

Yes, it applies to JavaScript and TypeScript projects by detecting available tooling directly from your package.json and optional configurations, then executing concrete commands without guessing.

A PR gauntlet prevents risky code from being merged by performing a residue sweep that flags large or binary additions in your changed files, reporting them clearly alongside standard formatting and lint failures.

Diff-scoped preflight fixes the base ref and changed-file set so pull request readiness checks reflect exactly the code you are about to submit, validating only the changes between your branch and the base commit.

The deterministic gate sequence runs typecheck, lint, format, and tests in order, stopping immediately on the first failure to reduce noise and report the exact failing files without running subsequent checks.