checking-pr-readiness

Assesses whether a git branch is ready for pull request creation using evidence-based checks.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/jrgilbertson/the-rookery --skill checking-pr-readiness-jrgilbertson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checking-pr-readiness
Source: https://github.com/jrgilbertson/the-rookery/tree/main/skills/checking-pr-readiness
Command: npx skills add https://github.com/jrgilbertson/the-rookery --skill checking-pr-readiness-jrgilbertson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Deciding whether a branch is truly ready for a pull request often relies on gut feel or green CI alone, letting unreviewed code, missing changelog entries, stale evidence, and transient artifacts slip through. This Skill runs a read-only readiness gate that gathers the full working surface, verifies upstream review steps from receipts, and produces a recommendation with numbered options before any PR is opened. ## Core Features & Use Cases - Working surface gather: Enumerates committed, staged, unstaged, and untracked paths against the merge base, and flags transient artifacts that would ship with the change. - Receipt-based verification: Records code review, simplification, browser testing, design critique, and learning capture with a closed set of status words, refusing Approve when evidence is missing. - Pre-PR sweep checks: Runs bundled shell helpers for changelog entries, evidence freshness, and diff size caps, deferring to repository-owned gates when they exist. - Use Case: Before opening a PR on a feature branch, ask the agent to check PR readiness; it reports a recommendation such as approve, request changes, or stop and file follow-up, then waits for your numbered reply. ## Quick Start Ask the agent to check whether the current branch is ready for a pull request and wait for its recommendation and numbered options.

Frequently Asked Questions about checking-pr-readiness

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

FAQPage Schema
How do I check if a branch is ready for a pull request?▼

Run this readiness gate on the branch: it enumerates committed, staged, unstaged, and untracked paths against the merge base, verifies upstream review steps from receipts, and returns an approve, request-changes, or stop recommendation with numbered options.

What checks run before opening a pull request?▼

The gate gathers the working surface, discovers repository-owned hooks and CI gates, verifies code review and simplification receipts, compares delivered work against the linked issue or brief, checks the learning signal, and runs sweep classes including changelog entry and diff size.

Does this skill open or merge the pull request itself?▼

No. The gate is read-only and never stages, commits, pushes, opens, or merges. On an Approve reply it hands an evidence pack to an installed PR-opening companion skill, which owns publication.

Why is Approve withheld even when CI is green?▼

Green CI is not evidence that upstream steps ran. Approve requires a complete gather: every applicable check must be verified by a named receipt, not applicable, or honestly recorded as not verified, and any incomplete enumeration blocks approval.

What happens when a companion skill or tool is missing?▼

The dependent check is recorded as skipped with the missing dependency named, and the remaining checks still run. A skipped class only normalizes to verified when an equivalent repository-owned gate is present and verified in the same session.