check-pr-readiness

What problem does it solve?

It prevents broken or low-quality code from landing in a pull request by running a consistent pre-flight check across the branch’s actual diff, then stopping immediately on the first failing gate.

Core Features & Use Cases

• Diff-scoped gauntlet: Computes the base range and checks only what changed (plus relevant residue signals from added lines).
• Tooling-aware detection: Identifies the project’s real commands for typechecking, linting, formatting, and testing instead of guessing.
• Strict failure semantics: Stops at the first red gate, reports the exact reproduction command, and never silently fixes code (except offering format auto-fix when supported).
• Residue sweep: Flags likely “forgotten” issues in the diff such as console.log, debugger statements, .only/.skip, newly added TODOs/FIXMEs, and large/binary additions.
• Use case: Before pushing a PR, ensure production readiness and catch common review blockers like type errors, formatting drift, flaky residue, or unintended file changes.

Quick Start

Run pre-pr check so the skill evaluates your branch against the base and reports whether it’s PR-ready or blocked.