skills.rest
diazMelgarejo
diazMelgarejoCOMMUNITY
Explore all skills by this author →
Website𝕏@Melgarejo_yDiazGitHub

stacked-pr-naming

Standardizes stacked PR branch names and titles so merge order is explicit.

Updated Mar 22, 2026
Search Tags:#git workflow#github#pull requests#rebase#branch naming#merge order#stacked prs
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill stacked-pr-naming-diazmelgarejo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stacked-pr-naming
Source: https://github.com/diazMelgarejo/orama-system/tree/main/bin/orama-system/skills/stacked-pr-naming
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill stacked-pr-naming-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When opening multiple dependent pull requests against the same integration base, unclear branch names and titles make merge order ambiguous and cause wrong-base PRs. This Skill enforces a canonical naming convention so PR(N+1) is always based on PR(N) and the merge sequence is visible in the PR title. ## Core Features & Use Cases - Canonical branch naming: Branches follow the stack/NN-short-topic format with zero-padded numbering derived from the repo's integration base. - Structured PR titles: Titles follow [NN/TT → <integration-base>] <type>: <summary> so stack position and target base are obvious at a glance. - Merge-order and base rules: NN=00 targets the integration branch, NN>00 targets stack/(NN-1)-…, and PR(N+1) is rebased on PR(N) before opening. - Use Case: While shipping a security remediation split into four dependent PRs, name them stack/00-… through stack/03-…, title each [NN/4 → merged] fix: …, and merge them in order without wrong-base conflicts. ## Quick Start Ask the agent to create a stacked PR series for your dependent changes using the stack/NN branch naming and [NN/TT → base] title format.

Frequently Asked Questions about stacked-pr-naming

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

FAQPage Schema
How do I name branches for stacked pull requests on GitHub?▼

Use the stack/NN-short-topic format with zero-padded numbers, creating stack/00 from the integration base and each stack/(N+1) branch from stack/NN after it is pushed. This keeps the dependency chain explicit in branch names.

What should a stacked PR title look like?▼

Use the format [NN/TT → <integration-base>] <type>: <summary>, where NN is the position, TT is total stack width, and the arrow shows the target base. The PR body's first lines should list Stack, GitHub base, and Depends on.

What base branch should each PR in a stack target?▼

The first PR (NN=00) targets the repo's integration branch, and every subsequent PR targets stack/(NN-1), the branch of the PR before it. This ensures PR(N+1) is always based on PR(N).

Can I rebase an existing remote branch in a stack?▼

Force-updating or rebasing an existing remote branch requires explicit approval first under this Skill's ask-first boundary. The same applies to changing the total stack width TT after PRs are already open.

When should I not use stack/NN branch naming?▼

Do not use dated yyyy-mm-dd-NNN names as a substitute for stack/NN naming within a stack, and never open stack PRs against the wrong integration base, such as periscope's main instead of merged.

Related Skills

Explore More Software Engineering Skills→
Dev10x-GuruDev10x-Guru
7

Dev10x:git-commit-split

Split large git commits into smaller atomic commits via interactive rebase.

Official
Advanced
open-horizon-labsopen-horizon-labs
3

oh-merge

Batch-review and merge stacked GitHub PRs in dependency order.

Official
Advanced
constellosconstellos
5

Stacked PR Management

Create dependent PR chains with base/child relationships using GitHub CLI.

Official
Advanced
raydocsraydocs

flow-impl-review

Review code diffs for quality, security, and architecture.

Community
Advanced