kata-stacked-pr-create

Decompose large feature work items into stacked GitHub pull requests.

Updated Sep 3, 2025
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-stacked-pr-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kata-stacked-pr-create
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-stacked-pr-create
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-stacked-pr-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you break down a large feature work item into a chain of stacked pull requests that are independently reviewable, reducing review risk and enabling safer incremental merges.

Core Features & Use Cases

  • Decision-gated stack planning: counts high signals (scope size, acceptance criteria count, pillar coverage, obvious layering, and independence) and checks anti-signals (hotfix/incident, cross-fork PRs, monolithic refactors) before proceeding.
  • Layer decomposition + traceability: confirms and records per-layer covered acceptance criteria, touched components, and produces PR bodies that reference the umbrella issue with Refs/Closes semantics.
  • End-to-end PR creation workflow: creates a shared worktree, builds sequential layer branches, opens PRs with correct bases (layer 1 → main; layers 2..N → previous layer), and mirrors labels/assignees/reviewers from CODEOWNERS.
  • Safety and quality guardrails: requires explicit user confirmation, avoids UI merges during creation, prevents manual application of size labels, and enforces per-PR quality gating for each layer.
  • Optional git-spice variant: supports an alternate operational path using git-spice with equivalent planning logic and stacked submission behavior.

Quick Start

Use the kata-stacked-pr-create skill to create a stacked PR plan and then generate the PR chain for an umbrella issue after confirming the proposed layer decomposition.

Frequently Asked Questions about kata-stacked-pr-create

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

FAQPage Schema
What are stacked pull requests and why use them for large features?

Stacked pull requests decompose a large feature into a sequential chain of independently reviewable PRs, reducing review risk and enabling safer incremental merges across technical layers like schema, API, and UI.

How do I create a stacked PR chain from a GitHub issue?

To create stacked PRs, the workflow validates issue quality, requires explicit confirmation of layer decomposition, creates a shared git worktree, and opens sequential PRs with correct bases alongside mirrored labels and CODEOWNERS reviewers.

Does stacked PR creation work with git worktrees and CODEOWNERS?

Yes, stacked PR creation uses a shared git worktree to build sequential layer branches and automatically mirrors labels, assignees, and reviewers across every PR based on your CODEOWNERS file.

Can I use git-spice to submit stacked PRs on GitHub?

Yes, an optional git-spice variant supports an alternate operational path for stacked submission with equivalent planning logic, validating scope size and acceptance criteria before opening sequential PRs.

When should I avoid breaking work into stacked PRs?

Avoid stacked PRs for hotfixes, incident responses, cross-fork PRs, or monolithic refactors, as the workflow checks these anti-signals to ensure changes have natural technical layers and independence.

How does stacked PR creation handle issue traceability and merging?

Stacked PR creation maintains traceability by recording per-layer covered acceptance criteria and generating PR bodies that reference the umbrella issue with Refs or Closes semantics, preventing unsafe UI merges during creation.