skills.rest
dwayneparton
dwaynepartonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

github-resolve-stack

Orchestrates parallel review-comment resolution across GitHub stacked pull requests.

1|Updated Mar 12, 2026
Search Tags:#code review#github#orchestration#rebase#gh cli#copilot#stacked prs
One-click install
npx skills add https://github.com/dwayneparton/claude --skill github-resolve-stack-dwayneparton
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-resolve-stack
Source: https://github.com/dwayneparton/claude/tree/main/skills/github-resolve-stack
Command: npx skills add https://github.com/dwayneparton/claude --skill github-resolve-stack-dwayneparton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Resolving Copilot review comments across a stack of dependent GitHub PRs is error-prone: fixes in lower PRs must propagate upward, parallel work risks file conflicts, and per-PR fixes can drift from the stack's overall intent. This Skill coordinates the whole stack so review-driven changes stay consistent across layers. ## Core Features & Use Cases - Stack discovery and intent capture: Uses the gh stack extension to map PR dependencies, records each PR's role, and builds a file-overlap map to plan safe parallelism. - Wave-based parallel sub-agents: Fans out Sonnet or Opus agents per PR based on diff size, comment complexity, and stack position, with each agent running /github-resolve in an isolated git worktree. - Cascade propagation and stack review: Rebases upper PRs onto lower-PR fixes with gh stack rebase, re-runs CI gates on rebased heads, and performs a final whole-stack intent, layering, and consistency review. - Use Case: You have a four-PR stack (schema, repository, API, UI) with Copilot comments on each. The Skill discovers the stack, resolves comments bottom-up with parallel agents where files don't overlap, propagates fixes upward, and reports one consolidated summary. ## Quick Start Ask the agent to run the github-resolve-stack skill on the current PR's stack to resolve all Copilot review comments across every PR in the stack.

Frequently Asked Questions about github-resolve-stack

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

FAQPage Schema
How do I resolve Copilot review comments across a stacked PR workflow?▼

Run this Skill on any PR in the stack. It discovers the full stack with gh stack, launches one sub-agent per PR running /github-resolve in isolated worktrees, propagates lower-PR fixes upward via cascade rebases, and delivers one consolidated report.

What is the difference between github-resolve and github-resolve-stack?▼

github-resolve owns a single PR: triaging Copilot comments, fixing, pushing, and looping. github-resolve-stack is the layer above it, coordinating which PRs exist, their dependency order, fix propagation between layers, and whole-stack intent consistency.

Does this work with GitHub PRs that are not linked as a stack?▼

Yes, with a fallback. If gh stack checkout finds nothing, it walks base branches manually using gh pr list to reconstruct the chain, then does bottom-up rebases by hand. It offers to run gh stack link afterward but never links PRs itself.

When does the stack orchestrator stop and ask for human decisions?▼

It pauses when a sub-agent flags items that would alter the stack's intent or scope, when a propagation rebase hits a non-mechanical conflict, or when the stack-level review finds drift. Flagged items are asked via AskUserQuestion and never posted to GitHub.

Can sub-agents rebase or force-push branches in the stack?▼

No. Sub-agents never rebase, force-push, or merge. Only the orchestrator performs rebases, exclusively through gh stack rebase and gh stack push, which uses force-with-lease, during the step 7 propagation cascade.

How are Sonnet and Opus models chosen for each PR in the stack?▼

Each PR is scored on diff size, comment count and nature, file overlap, and stack position. Sonnet is used only when every signal leans simple; any design-level, cross-file, or high-blast-radius signal selects Opus.

Related Skills

Explore More Software Engineering Skills→
doragedorage

gh-stack

Automate stacked branch and pull request management with the gh-stack GitHub CLI extension.

Community
Advanced
smallorbitsmallorbit

merge-stack

Merge multi-PR chains bottom-up with squash strategy and retargeting.

Community
Advanced
vultisigvultisig
40

fix-pr-comments

Triage CodeRabbit PR feedback and apply fixes with separate commits.

Official
Advanced
corygabrielsencorygabrielsen
1

loop-address-pr-feedback

Collect, triage, fix, and reply to PR review feedback across stacked PRs.

Community
Advanced