check-pr-readiness

Name: check-pr-readiness
Availability: InStock
Author: AgentSystemLabs

Run diff-scoped typechecking, linting, formatting, and tests on pull requests.

121|2|Updated Apr 24, 2026

Search Tags:#code quality #pull request #formatting #test suite #lint #git diff #typecheck

Ready to run

npx skills add https://github.com/AgentSystemLabs/core --skill check-pr-readiness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-pr-readiness
Source: https://github.com/AgentSystemLabs/core/tree/main/plugins/agentsystem-core/skills/check-pr-readiness
Command: npx skills add https://github.com/AgentSystemLabs/core --skill check-pr-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about check-pr-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check pull request readiness before merging a branch?▼

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.

What is diff-scoped linting and typechecking for a pull request?▼

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.

How do I catch console.log and debugger statements left in my code before pushing?▼

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.

Can I auto-fix formatting issues during a pull request readiness check?▼

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.

Does the pull request check work with my project's existing typecheck and test commands?▼

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.

Why does my pull request readiness check stop at the first failing gate?▼

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.