smith-stacks

Coordinate stacked PR workflows with enforced merge order across branches.

1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/tianjianjiang/smith --skill smith-stacks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smith-stacks
Source: https://github.com/tianjianjiang/smith/tree/main/smith-stacks
Command: npx skills add https://github.com/tianjianjiang/smith --skill smith-stacks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

Stacked PR workflows help teams coordinate large feature work by breaking changes into smaller, independently reviewable PRs and maintaining a clear dependency chain.

Core Features & Use Cases

  • Stack creation and management: define base PRs and dependent branches, enforce merge order, and handle squash merges when appropriate.
  • Scope verification and guardrails: load stack metadata, enumerate branches, obtain explicit scope approval, and report status across the stack.
  • Collaboration pattern: improve parallel workability and reduce integration risk by aligning reviewers and change sets.

Quick Start

Create a base PR for a feature, then create child PRs from that base and merge bottom-up.

Frequently Asked Questions about smith-stacks

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

FAQPage Schema
What is the best way to manage stacked PRs for large features?

Managing stacked PRs involves breaking large features into smaller, independently reviewable branches and enforcing a strict merge order from the bottom up. This coordinates dependent pull requests and reduces integration risk.

How do I coordinate dependent pull requests and enforce merge order?

Coordinate dependent pull requests by defining a base PR and creating child branches from it. Enforce merge order by validating scope, loading stack metadata, and merging changes bottom-up to maintain the dependency chain.

How does stacked branch management improve code review workflows?

Stacked branch management improves code review workflows by aligning reviewers with smaller, focused change sets. This parallel workability reduces integration risk and ensures dependent branches merge in the correct sequence.

Do I need to install gh and jq to automate stacked PR workflows?

Yes, automating stacked PR workflows requires installing the gh and jq command-line dependencies. These tools process stack metadata, validate branch scope, and execute pull request operations safely.

Can I handle squash merges when coordinating dependent branches?

Yes, you can handle squash merges when coordinating dependent branches. The workflow enforces merge order and adjusts the stack metadata appropriately to maintain the integrity of the dependency chain.

What are the limitations of stacked branch management for pull requests?

Stacked branch management requires strict scope verification and explicit approval prior to operations. Limitations include potential complexity in rebase conflicts if base branches change, requiring careful metadata validation to prevent broken dependency chains.