Executes stacked pull request plans with per-layer build, test, and lint gates.
npx skills add https://github.com/azure-id/orc --skill orc-pr-driver-azure-id
Please help me install this Agent Skill. Skill: orc-pr-driver Source: https://github.com/azure-id/orc/tree/main/templates/skills/orc-pr-driver Command: npx skills add https://github.com/azure-id/orc --skill orc-pr-driver-azure-id
stacked-pr/<slug>/stack-plan.md and refuses to run on incomplete plans (missing ticket, unanswered decisions, fewer than 2 layers, red build). - Snapshot-protected splitting: Commits the existing worktree to a snapshot branch before touching any branch, then materializes each layer file-by-file with a completeness check proving nothing was dropped. - Mandatory per-layer green gate: Runs build, scoped tests, lint attributed to each layer's own base, and the repo's pre-commit hooks — never --no-verify, never submitting a red layer. - Stack lifecycle management: Submits via gh stack submit, writes PR bodies from templates, and handles sync, rebase, conflict resolution, and bottom-up merging. - Use Case: After planning a 4-layer stack with /orc-pr-setup, run this Skill to create one branch and PR per layer, verify each layer passes CI independently, and merge them bottom-up as reviews complete. ## Quick Start Ask the assistant to run /orc-pr-driver to build and submit the stacked pull requests from your approved stack plan.High-intent search queries and answers about installing and using this skill.
Create a stack plan with /orc-pr-setup or `orc pr stack template <slug>`, then run /orc-pr-driver. It uses the github/gh-stack extension to create one branch per layer, submits them with `gh stack submit`, and chains each PR's base to the layer below.
The driver snapshots your existing worktree into a temporary branch, then materializes each layer file-by-file from the plan's file list. Splits are file-granular only — hunk surgery and partial-file splits are forbidden, and a completeness check verifies no file was dropped.
No. GitHub stacked PRs cannot cross forks, so the driver's preflight checks fail on a fork and it recommends a single regular PR instead. The repository must also have gh 2.0+ and the github/gh-stack extension installed.
A foundation layer that declares a function only a higher layer calls is genuinely dead code as a standalone PR. The driver stops and asks whether to merge the layers, move the first caller down, or add an explicit reasoned suppression — it never suppresses silently.
Amending a layer rewrites every branch above it, so previously-green upper layers can go red. The driver runs `gh stack rebase --upstack` and re-runs the full build-test-lint gate at every layer above the change, bottom-up.
Avoid stacking for changes spanning multiple repositories (unsupported by GitHub), on forks, or when the change fits one reviewable PR. Above 6 layers the planner warns, and above 8 it stops, since each layer costs a full CI run and review cycle.
christian-byrneAnalyze implementation plans to recommend Pull Request splitting strategies.
maximhqResolve unresolved PR review comments across a Graphite stack of branches bottom-up.
bitsoexIntegrates Java projects with SonarQube via MCP Server for automated code quality analysis and issue resolution.
MS33834Stages, commits, pushes, and opens a GitHub pull request for a linear change.