skills.rest
mkaczkowski
mkaczkowskiCOMMUNITY
Explore all skills by this author →
GitHub

stacked-prs

Organize large feature work into dependent pull requests with conventional commit titles.

3|Updated Sep 16, 2025
Search Tags:#branching#code-review#pull-requests#git-workflow#conventional-commits#stacked-prs
One-click install
npx skills add https://github.com/mkaczkowski/ai-command-library --skill stacked-prs-mkaczkowski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stacked-prs
Source: https://github.com/mkaczkowski/ai-command-library/tree/main/plugins/pr/skills/stacked-prs
Command: npx skills add https://github.com/mkaczkowski/ai-command-library --skill stacked-prs-mkaczkowski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a series of dependent pull requests that build on each other, enabling incremental review and controlled integration for large features.

Core Features & Use Cases

  • PR stacking with dependent branches to ensure incremental reviews.
  • Conventional-commit based PR titles for clear traceability.
  • Structured branch layout and PR bodies to coordinate multi-PR releases.

Quick Start

Create a base PR and then add subsequent dependent PRs in a stacked sequence using conventional commit titles.

Frequently Asked Questions about stacked-prs

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

FAQPage Schema
How do I manage dependent pull requests for a large feature branch?▼

Managing dependent pull requests involves organizing large feature work into a stacked sequence of PRs using conventional commit titles. This approach ensures incremental code review and controlled integration for complex features by prescribing branch layout and stacking order.

What is the best way to structure a stacked PR workflow?▼

The best way to structure a stacked PR workflow is to create a base pull request and then add subsequent dependent PRs in a sequence. This requires a structured branch layout and clear ticket references in conventional commit-based PR titles.

Why use conventional commits for stacked pull requests?▼

Using conventional commits for stacked pull requests provides clear traceability across dependent branches. It satisfies structured workflow requirements by standardizing PR naming conventions, making it easier to coordinate multi-PR releases and track feature progression.

How do I coordinate a multi-PR release with dependent branches?▼

To coordinate a multi-PR release with dependent branches, you organize the work into a series of dependent pull requests. You must prescribe PR naming conventions, branch layout, PR bodies, and stacking order to enable controlled integration.

When do I need a stacked PR workflow for my git branches?▼

You need a stacked PR workflow when your project breaks complex features into multiple PRs and requires clear ticket references. This git workflow enables incremental review and controlled integration for large feature development.

Related Skills

Explore More Software Engineering Skills→
FelipePepeFelipePepe

rule-gitflow

Enforce standardized Git workflows with Conventional Commits and Husky hooks.

Community
Intermediate
rarestgrarestg
1

merge-stack

Merge dependent GitHub Pull Requests sequentially into the main branch.

Community
Intermediate
ElbertePlinioElbertePlinio

create-pr

Generate Conventional Commits PR titles, templated bodies, and run local checks.

Community
Intermediate
howarewoohowarewoo

commit

Manage code commits and pull request updates with Graphite and GitHub CLI.

Community
Advanced