pr-ready

Diagnose PR workflow readiness and drift for a concrete target.

4|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill pr-ready-danielbaustin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-ready
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/pr-ready
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill pr-ready-danielbaustin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose PR workflow readiness and drift for a concrete target and emit a structured readiness result.

Core Features & Use Cases

  • Diagnose readiness across issues, task bundles, branches, or worktrees.
  • Classify states as ready, ready_with_repairs, or blocked and report preflight separately.
  • Apply only very small, bounded repairs when allowed.
  • Emit a deterministic, machine-readable readiness artifact that guides handoff.

Quick Start

Resolve a concrete target (issue_number, task_bundle_path, branch, or worktree_path) and run the canonical doctor surface to produce a readiness result.

Frequently Asked Questions about pr-ready

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

FAQPage Schema
How do I diagnose PR readiness and drift before merging a branch?▼

PR readiness and drift diagnosis runs the canonical doctor surface to classify a branch, issue, or worktree as ready, ready_with_repairs, or blocked, providing a structured readiness result to guide handoff.

What is PR drift and how does it affect my git workflow?▼

PR drift occurs when a branch or worktree diverges from its expected state. Diagnosing it applies the doctor surface to inspect the target and reports preflight gating separately to identify blocking issues.

Can I automatically apply repairs when checking PR readiness?▼

Yes, PR readiness diagnosis can apply very small, bounded repairs when permitted, classifying the result as ready_with_repairs to ensure only safe, minor fixes are automatically applied.

Does PR readiness diagnosis require specific dependencies to run?▼

No dependencies are required. The diagnosis prefers the canonical doctor output via adl/tools/pr.sh doctor --json, falling back to ready or preflight surfaces or direct inspection if needed.

What is the best way to get a machine-readable PR readiness report?▼

The best way to get a machine-readable PR readiness report is running the doctor surface, which emits a deterministic readiness artifact classifying the target state and reporting preflight gating separately.

Why is my PR blocked and how do I identify preflight gating issues?▼

A PR is blocked when preflight gating fails. The diagnosis resolves a concrete target like an issue_number or task_bundle_path and reports these preflight failures separately from the main readiness classification.