What tools are required to use this skill?

This skill requires git-town for branch management, the GitHub CLI (gh) for PR creation, and the just command runner to execute the automation scripts.

How does the skill handle different phases of development?

It uses logic to detect your current branch; if you are on main, it initiates a 'new-stack' for Phase 1. If you are on an existing phase branch, it uses 'append-stack' to link Phase N to Phase N-1.

What is a stacked PR?

A stacked PR is a sequence of pull requests where each one depends on the one before it. This allows developers to submit small, atomic changes for review while continuing to build the next part of the feature.

Will my internal thought logs be committed to GitHub?

No, the skill is specifically designed to exclude the thoughts/ directory from all commits to ensure your repository history remains clean and professional.

Stacked PR Workflow

Name: Stacked PR Workflow
Author: elliotsteene

byelliotsteene

0•

Productivity & Workflow

Automates the creation and management of sequential, stacked pull requests for multi-phase software implementations.

The Stacked PR skill streamlines the transition from local implementation to code review by leveraging git-town to manage complex branch dependencies. It enables Claude to automatically package each phase of a project into an atomic PR that builds upon the previous one, ensuring a clean review process while allowing development to continue seamlessly. By handling branch naming, commit formatting, and PR metadata automatically, it reduces the cognitive overhead of managing multi-part features and ensures that internal thought logs remain excluded from the repository history.

Key Features

01Standardized commit message and PR body generation for better readability

02Integrated stack synchronization to propagate changes across branch chains

030 GitHub stars

04Automated branch creation and naming using git-town integration

05Sequential PR stacking with automatic base branch detection for PRs

06Automatic exclusion of internal thoughts/ directories from commits

Use Cases

01Breaking down large feature implementations into smaller, reviewable segments

02Maintaining a linear development flow during complex refactoring tasks

03Managing multi-phase implementation plans without manual Git branch overhead

Key Features

01Standardized commit message and PR body generation for better readability

02Integrated stack synchronization to propagate changes across branch chains

030 GitHub stars

04Automated branch creation and naming using git-town integration

05Sequential PR stacking with automatic base branch detection for PRs

06Automatic exclusion of internal thoughts/ directories from commits

Use Cases

01Breaking down large feature implementations into smaller, reviewable segments

02Maintaining a linear development flow during complex refactoring tasks

03Managing multi-phase implementation plans without manual Git branch overhead