git-spice-stack-prs

Manage stacked GitHub pull requests with git-spice for branch creation, submission, restacking, and updates.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/corymhall/toolkit --skill git-spice-stack-prs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-spice-stack-prs
Source: https://github.com/corymhall/toolkit/tree/main/general/skills/git-spice-stack-prs
Command: npx skills add https://github.com/corymhall/toolkit --skill git-spice-stack-prs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the management of stacked GitHub pull requests, ensuring that local branch history and remote PRs remain synchronized throughout complex development workflows.

Core Features & Use Cases

  • Automated Stack Management: Handles branch creation, submission, restacking, and updates for stacked PRs.
  • Synchronization: Keeps GitHub PRs aligned with local Git history, crucial for maintaining a clean and manageable PR chain.
  • Use Case: When working on a feature that depends on several smaller, reviewable branches, this skill helps manage the entire stack from initial creation to final submission and updates.

Quick Start

Use the git-spice-stack-prs skill to submit the current stack of branches as draft pull requests.

Frequently Asked Questions about git-spice-stack-prs

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

FAQPage Schema
How do I manage stacked pull requests in GitHub?

This skill automates stacked pull request management by handling branch creation, submission, and restacking to keep local Git history synchronized with remote GitHub PRs throughout complex workflows.

What is stacked PR management and when do I need it?

Stacked PR management is the process of submitting dependent branches sequentially for code review. You need it when working on a large feature that depends on several smaller, individually reviewable branches.

Do I need git-spice and gh CLI to submit stacked branches as drafts?

Yes, you need both the git-spice CLI and the gh CLI installed for full functionality. These tools allow the skill to automatically submit your current stack of branches as draft pull requests on GitHub.

How do I restack branches after updating a pull request?

You can restack branches after updating a pull request by running this skill, which automatically synchronizes dependent branches and updates the GitHub PR chain to reflect changes in local Git history.

What's the best way to keep GitHub PRs aligned with local Git history?

The best way to keep GitHub PRs aligned with local Git history is using this skill for automated stack management, ensuring dependent branches remain synchronized cleanly during complex code review workflows.

Are there limitations when synchronizing a PR chain with git-spice?

A key limitation is the strict dependency on both git-spice and gh CLIs; without them, the automated synchronization of sequential code review branches across dependent chains will not function.