mergify-stack

Automate stacked Git branch and dependent pull request management.

64|2|Updated Nov 8, 2021
One-click install
npx skills add https://github.com/FlatbreadLabs/flatbread --skill mergify-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mergify-stack
Source: https://github.com/FlatbreadLabs/flatbread/tree/main/.agents/skills/mergify-stack
Command: npx skills add https://github.com/FlatbreadLabs/flatbread --skill mergify-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually managing stacked Git branches and dependent pull requests leads to broken PR relationships, inconsistent commit histories, and time-consuming interactive rebase operations, especially when working on multi-commit features that build on prior changes.

Core Features & Use Cases

  • Stack-based PR Management: Automatically links dependent commits into a stack of pull requests, maintaining correct relationships between changes.
  • Non-interactive Git Operations: Provides commands for rebasing, fixup, squashing, and reordering commits without spawning interactive editors, ideal for AI agent and automated workflows.
  • Revision History Tracking: Automatically records amend notes in PR revision history so reviewers can understand changes without diffing old commit SHAs.
  • Use Case: When developing a multi-part feature that requires 3 dependent commits, use this Skill to push all changes as a linked stack of PRs, automatically sync the stack when trunk updates, and ensure each PR passes CI independently.

Quick Start

Use the mergify-stack skill to create a new feature branch, make a series of dependent commits following conventional commits, and push them as a linked stack of pull requests with automatic CI and revision history tracking.

Frequently Asked Questions about mergify-stack

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

FAQPage Schema
How do I automate stacked pull requests for multi-commit feature branches?

Automating stacked pull requests involves linking dependent commits into a sequential PR stack, ensuring each PR passes CI independently while maintaining correct relationships between changes. This eliminates manual branch tracking and broken PR hierarchies.

What is the best way to rebase and reorder commits without spawning interactive editors?

Non-interactive Git operations allow you to rebase, fixup, squash, and reorder commits without spawning interactive editors, making them ideal for AI agent workflows and automated commit management pipelines.

How does revision history tracking work for amended commits in a pull request?

Revision history tracking for amended commits automatically records amend notes in the PR revision history, allowing reviewers to understand changes without manually diffing old commit SHAs or making GitHub edits.

Can I sync pull request metadata automatically from conventional commit messages?

Yes, you can sync pull request metadata automatically from commit messages. This ensures PR metadata stays synchronized with the actual commit history as the stack updates.

How do I resolve conflicts in dependent code changes across a stack of pull requests?

Resolving conflicts in dependent code changes across a PR stack requires automatic synchronization of the entire stack when the trunk updates, ensuring dependent branches rebase cleanly against the latest changes.