using-git-spice

Manage stacked Git branches and Change Requests with git-spice commands.

19|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/arittr/spectacular --skill using-git-spice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-git-spice
Source: https://github.com/arittr/spectacular/tree/main/skills/using-git-spice
Command: npx skills add https://github.com/arittr/spectacular --skill using-git-spice

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git-spice.

What problem does it solve?

This Skill eliminates the complexity of managing stacked Git branches and dependent Pull/Change Requests, providing clear guidance and automating tedious rebasing and submission tasks. It helps developers avoid common pitfalls and maintain a clean, reviewable Git history.

Core Features & Use Cases

  • Stacked Branch Management: Automates the creation, rebasing, and submission of dependent branches, ensuring a clean and organized Git history.
  • Command Reference & Workflows: Provides a quick reference for git-spice commands and guides through common workflows like creating a stack, updating branches after review, and syncing with upstream.
  • Error Prevention: Highlights common mistakes and anti-patterns, ensuring you use git-spice effectively without breaking stack relationships.
  • Use Case: Streamline feature development by managing a series of dependent changes as a single, reviewable stack of PRs, ensuring clean history and easy collaboration.

Quick Start

Initialize your repo

gs repo init

Create a new stacked branch

gs branch create my-feature

View your stack

gs log short

Frequently Asked Questions about using-git-spice

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

FAQPage Schema
How do I manage dependent branches without manually rebasing in Git?

Stacked branches let you organize dependent changes as a series of PRs that maintain parent-child relationships. git-spice automates rebasing and syncing so you don't have to manually rebase when upstream changes—it preserves stack integrity automatically.

What's the best way to organize multiple related pull requests?

Create a stack: a chain of branches where each PR depends on the one below it. git-spice handles creation, rebasing, and submission, so reviewers see clean, reviewable diffs and you avoid tangled merge histories.

How do I update my stacked branches after code review feedback?

Make changes to the branch being reviewed, then use git-spice to restack—it automatically rebases dependent branches upstack without breaking relationships or losing your work.

Can I use stacked branches with my existing Git workflow?

Yes. git-spice wraps standard Git commands and works alongside your current workflow. Initialize with `gs repo init`, then use `gs branch create` and `gs log` to manage stacks while keeping your repository and remotes intact.

What common mistakes should I avoid when managing stacked branches?

Don't use direct `git rebase` on stacked branches—use `gs restack` instead to preserve relationships. Avoid force-pushing without syncing upstack changes, and don't merge intermediate branches prematurely.

Do I need to learn new commands to work with stacked branches?

git-spice provides a small command set: `gs repo init`, `gs branch create`, `gs log`, and `gs restack` cover core workflows. A quick reference guides you through syncing with upstream and submitting stacks.