skills.rest
dukebw
dukebwCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

stack-pr

View and export stacked PRs while preserving stack-info in commits.

1|Updated Dec 5, 2025
Search Tags:#git#commit history#view#stacked PRs#export#PR management#stack-pr
One-click install
npx skills add https://github.com/dukebw/dotfiles --skill stack-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stack-pr
Source: https://github.com/dukebw/dotfiles/tree/main/.claude/skills/stack-pr
Command: npx skills add https://github.com/dukebw/dotfiles --skill stack-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stacked PRs often require careful tracking across multiple dependent branches. This Skill provides a streamlined way to view and export the complete PR stack while preserving stack-info for traceability.

Core Features & Use Cases

  • View stacked PRs with stack-pr view to verify the complete stack and the mapping between PR numbers and branches.
  • Export the verified stack with stack-pr export, including the option to specify a base and head range for the export.
  • Maintain stack-info in commits and documentation to ensure traceability across reviews and merges.

Quick Start

Use the stack-pr tool to view the current PR stack with stack-pr view. When ready to export, run stack-pr export -B <base> -H <head> to push the selected range, and keep the stack-info line in commit messages.

Frequently Asked Questions about stack-pr

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

FAQPage Schema
How do I view stacked PRs to verify the mapping between branches and PR numbers?▼

Use the stack-pr view command to verify the complete PR stack and visualize the mapping between PR numbers and their corresponding branches.

How do I export a specific range of stacked PRs while preserving stack-info?▼

Run stack-pr export with the -B <base> and -H <head> flags to push a selected range of stacked PRs while preserving the stack-info line in commit messages for traceability.

When do I need to maintain stack-info in my commit messages?▼

Maintain stack-info in commit messages when tracking multiple dependent PRs across branches to ensure complete traceability across collaborative code reviews and merges.

Can I specify a base and head range when exporting a PR stack?▼

Yes, you can specify a base and head range during PR stack export by passing the -B <base> and -H <head> parameters to push only the selected commits.

Does exporting stacked PRs keep the stack-info line for traceability?▼

Exporting stacked PRs preserves the stack-info line in commit messages, ensuring that traceability across dependent branches is maintained during the push and review process.

Related Skills

Explore More Software Engineering Skills→
ESO-ToolkitESO-Toolkit
2

rebase

Automate rebasing stacked Git branches after a squash merge.

Official
Advanced
edfentonedfenton
3

github-merge-stack

Merge stacked pull requests into main with squash merges.

Community
Advanced
FlatbreadLabsFlatbreadLabs
64

mergify-stack

Automate stacked Git branch and dependent pull request management.

Official
Advanced
arittrarittr
19

using-git-spice

Manage stacked Git branches and Change Requests with git-spice commands.

Community
Advanced