skills.rest
hyperjumptech
hyperjumptechOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-town-stacked-changes

Orchestrate stacked Git Town branches for incremental PR merges.

1|1|Updated Jan 5, 2026
Search Tags:#branching#feature-flags#incremental-delivery#pr-management#git-town#stacked-changes#ticket-batches
One-click install
npx skills add https://github.com/hyperjumptech/mediapulse --skill git-town-stacked-changes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-town-stacked-changes
Source: https://github.com/hyperjumptech/mediapulse/tree/main/.cursor/skills/git-town-stacked-changes
Command: npx skills add https://github.com/hyperjumptech/mediapulse --skill git-town-stacked-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables shipping features as a sequence of small, auditable PRs by stacking branches with Git Town so each layer can be reviewed and merged independently while preserving correct dependency order.

Core Features & Use Cases

  • Stack-based branching for incremental delivery, where each ticket layer depends on the previous one.
  • Gate risky changes with feature flags and plan removal of gates when the stack is complete.
  • Use with /prd-to-tickets workflows to map ticket batches to branches and PR bases.

Quick Start

Start the first independent slice with the base ticket, then add dependent tickets on top of the stack as they are ready.

Frequently Asked Questions about git-town-stacked-changes

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

FAQPage Schema
How do I ship dependent feature branches as stacked PRs?▼

You can ship dependent feature branches as stacked PRs by using Git Town stacks to enforce incremental merge order, ensuring each layer is reviewed and merged independently while preserving correct dependency order.

What is the best way to manage feature flag removal across a stacked branch workflow?▼

Managing feature flag removal across stacked branches involves gating risky changes with flags and planning the removal of those gates when the entire stack is complete and merged.

How do I map ticket batches to branches for incremental delivery?▼

You can map ticket batches to branches and PR bases by using /prd-to-tickets workflows alongside stack-based branching, where each ticket layer depends on the previous one for incremental delivery.

Can I review and merge dependent branches independently without breaking the merge order?▼

Yes, you can review and merge dependent branches independently by stacking branches with Git Town, which orchestrates deterministic branch orchestration and PR base management to preserve correct dependency order.

How do I start building a stack of small, reviewable pull requests?▼

To start building a stack of reviewable PRs, begin with the first independent slice using the base ticket, then add dependent tickets on top of the stack as they become ready.

Related Skills

Explore More Software Engineering Skills→
terrazul-aiterrazul-ai

response-draft

Generate draft responses for batches of open tickets using templates.

Official
Advanced
tianjianjiangtianjianjiang
1

smith-stacks

Coordinate stacked PR workflows with enforced merge order across branches.

Community
Advanced
mrp4stenmrp4sten
3

chained-pr

Coordinate chained and stacked GitHub PR workflows for large feature development.

Community
Advanced
t0labt0lab
2

branch-strategy

Enforce Git branch naming patterns and PR size limits.

Official
Intermediate