check-pr-readiness

To check pull request readiness, run a pre-pr check that evaluates your branch diff against the base. It runs diff-scoped typechecking, linting, formatting, and tests, stopping at the first failure and reporting whether your branch is ready or blocked.

Diff-scoped linting and typechecking evaluates only the code changes within a branch's computed base range. This prevents unintended file changes from failing the pull request check and focuses production-readiness guarantees on the actual modifications made.

To catch console.log and debugger statements, run a residue sweep on your diff. This pull request check flags likely left-behind code such as console.log, debugger statements, .only/.skip, newly added TODOs/FIXMEs, and large or binary additions.

You can auto-fix formatting issues during the pull request check only when a write-capable script exists. The check identifies your project's real formatting command and offers format auto-fix if supported, but never silently fixes code otherwise.

The pull request check works with your project's existing tooling by detecting the real commands defined for typechecking, linting, formatting, and testing instead of guessing. It executes these gates in a fixed order and reports pass or fail with exact reproduction commands.

A pull request readiness check stops at the first failing gate to prevent broken or low-quality code from landing. This strict failure semantics ensures you get the exact reproduction command for the specific failure, allowing you to fix the issue before checking subsequent gates.