pr-ready

Coordinate structured checks and whole-diff review to output a readiness verdict.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill pr-ready-mikecubed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-ready
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/flow/skills/pr-ready
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill pr-ready-mikecubed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a final, comprehensive readiness gate for branches or pull-request diffs, ensuring changes are ready for human review by integrating structured checks and a full-diff evaluation.

Core Features & Use Cases

  • Final integrated gate: coordinates structured checks and a whole-diff review to produce a clear readiness verdict.
  • Flexible roles and model selection: supports scout, structured-check, and final-reviewer roles with config-driven defaults.
  • Use Case: when a PR is nearly ready but requires one last high-signal pass before merge.

Quick Start

Activate this skill on a stable branch or diff to run the final readiness pass.

Frequently Asked Questions about pr-ready

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

FAQPage Schema
What is a PR readiness gate and how does it check a pull request diff?

A PR readiness gate automates final pull request evaluation by coordinating structured checks and a whole-diff review to produce a clear readiness verdict before human review.

How do I run a final readiness pass on a stable branch?

Activate the skill on your stable branch or diff to execute scout, triage, and structured-check steps, culminating in a whole-diff review and a durable readiness report.

Can I configure custom models for code review and structured checks?

Yes, the workflow supports scout, structured-check, and final-reviewer roles using project-configured or baked-in defaults to drive the automated diff review process.

When should I use an automated final readiness check instead of manual code review?

Use an automated final readiness check when a pull request is nearly ready for merge but requires one last high-signal evaluation pass to identify blockers.

Does the final readiness review identify blockers in the pull request?

Yes, the workflow performs end-to-end triage and a final whole-diff review to identify blockers and output a comprehensive readiness verdict for the branch.