orc-pr-setup

What problem does it solve? Large pull requests with thousands of lines across dozens of files are effectively unreviewable, leading to rubber-stamp approvals, risky big-bang merges, and painful reverts. This Skill decides where to cut one big change into an ordered chain of small, individually reviewable stacked pull requests. ## Core Features & Use Cases - Layer Planning: Groups changed files into ordered layers (schema → store → logic → adapter → wiring → transport → docs/flag) using a dependency graph, so each layer only depends on layers below it. - Measured Budgets: Uses real git diff --numstat numbers against configurable ceilings (lines per layer, files per layer, max layers) instead of guesses, with exclusions for generated code and lock files. - Uncertainty Gate: When a cut line is ambiguous, it stops and asks one decision at a time with costs and a recommendation, recording every answer in a ## Decisions audit trail. - Use Case: After building a 1,800-line payment feature, run the planner to split it into three reviewable PRs — a database migration, the store and domain logic, and the HTTP handler — each with a purpose, value class, and green-gate commands written into stacked-pr/<slug>/stack-plan.md. ## Quick Start Ask the assistant to plan stacked pull requests for the current change by invoking /orc-pr-setup and providing a ticket number.