pr-stack

Track stacked pull request states and dependencies in a JSON file.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/jpeggdev/buildwithjpegg --skill pr-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-stack
Source: https://github.com/jpeggdev/buildwithjpegg/tree/main/plugins/development-workflow/skills/pr-stack
Command: npx skills add https://github.com/jpeggdev/buildwithjpegg --skill pr-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps manage the complexity of working with stacked pull requests, ensuring that the state of your PRs and their dependencies is accurately tracked across different work sessions.

Core Features & Use Cases

  • Persistent State Tracking: Maintains a .claude/stack.json file to record the status and relationships of stacked PRs.
  • Automated Status Updates: Updates PR statuses (open, draft, merged) and base branches automatically based on Git and GitHub events.
  • Use Case: When working on a feature that requires multiple dependent PRs, this Skill ensures that the AI and you always know the current state of the stack, which PR is next, and how they relate to each other, preventing confusion and errors.

Quick Start

Use the pr-stack skill to review the current state of stacked pull requests.

Frequently Asked Questions about pr-stack

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

FAQPage Schema
How do I manage stacked pull requests across different development sessions?

You can manage stacked pull requests across sessions by persisting their state in a JSON file. This approach tracks PR status, branch dependencies, and base branch updates to maintain consistency for sequential feature development.

What is the best way to track stacked PR dependencies and status updates automatically?

Tracking stacked PR dependencies automatically involves recording PR statuses (open, draft, merged) and branch relationships in a persistent state file. This file enforces consistency between the local stack record and actual GitHub PR states.

Do I need the GitHub CLI installed to track stacked pull request states?

Yes, the GitHub CLI (`gh`) is required to track stacked pull request states. The skill depends on it to enforce consistency between your local JSON stack file and the actual remote PR states on GitHub.

How does a stack file handle base branch updates for sequential feature development?

A stack file handles base branch updates by tracking branch dependencies and triggering rebase operations when underlying PRs change. This ensures sequential feature development branches stay aligned with their updated parent branches.

Why does my stacked PR workflow lose track of branch relationships between sessions?

Stacked PR workflows lose track of branch relationships between sessions without persistent state tracking. Using a JSON file to record PR statuses and dependencies prevents this confusion by enforcing consistency with actual GitHub states.

Can I enforce consistency between local stack records and actual GitHub PR states?

Yes, you can enforce consistency between local stack records and actual GitHub PR states. The skill validates the JSON stack file against live GitHub data and triggers rebase operations to resolve any discrepancies.