stack

Automates Git-Spice stacked workflows to create, navigate and submit Change Requests.

1|1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/luan/agents --skill stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stack
Source: https://github.com/luan/agents/tree/main/pi/agent/extensions/git-tool/skill-resources/git-spice/stack
Command: npx skills add https://github.com/luan/agents --skill stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents error-prone, manual stacked-branch Git workflows by guiding you through creating, navigating, and submitting stacked Change Requests with Git-Spice instead of raw git and GitHub CLI commands.

Core Features & Use Cases

  • Stack branch creation & tracking: Create a branch stacked on the current branch (optionally without committing staged changes) and keep it tracked for stack operations.
  • Stack navigation & inspection: View the current stack, list all tracked branches, and move up/down/top/bottom to understand your stack shape.
  • Stack submit and restack workflows: Update and submit Change Requests, sync the repo to remove merged CR branches, and restack to reorder/rebase stack structure safely.
  • Example use case: You have an ongoing feature split into multiple dependent changes; create stacked branches for each piece, submit the resulting Change Requests, then restack after new commits arrive to keep dependencies consistent.

Quick Start

Tell the assistant: "Use the stack skill to create a new stacked branch named 'luan/my-feature' and then show me the current short stack log."

Frequently Asked Questions about stack

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

FAQPage Schema
How do I automate stacked branch workflows in Git without manual rebase commands?

Automating stacked branch workflows involves using Git-Spice stack commands to create, navigate, and submit dependent branches instead of raw git checkout, rebase, or push operations. This prevents error-prone manual stacked-branch Git workflows.

What is the best way to submit stacked pull requests when splitting a feature into dependent changes?

The best way to submit stacked pull requests for dependent changes is using Git-Spice to update and submit Change Requests while keeping the stack tracked. This maintains dependency consistency across branches without raw gh pr create commands.

How do I restack dependent branches after new commits arrive in the trunk?

Restacking dependent branches after new commits arrive requires running Git-Spice restack operations to reorder and rebase the stack structure safely. This keeps branch dependencies consistent when the trunk updates.

Does Git-Spice support moving changes between stacked branches?

Yes, Git-Spice supports moving changes between stacked branches. The stack workflow includes stack navigation commands to move up, down, to the top, or to the bottom of the stack, allowing you to understand the stack shape and transfer changes safely.

How do I sync my repository to remove merged stacked branches after a pull request is accepted?

Syncing a repository to remove merged stacked branches is handled by Git-Spice sync operations. This removes merged Change Request branches from your tracked stack and updates the remaining dependent branches automatically.

When should I use stacked change requests instead of a single large pull request?

Stacked change requests are ideal for trunk-safe development scenarios where ongoing work is split into multiple dependent branches. Use stacked branches when each piece of a feature builds on the previous one and must be updated, synced, and restacked over time.