pr

Create and coordinate stacked pull requests enforcing server-first merge order.

1|Updated May 20, 2026

Search Tags:#git #github #pr #code-review #branch-management #pull-request #stacked-pr

Ready to run

npx skills add https://github.com/mDevsLabs/mAI --skill pr-mdevslabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/mDevsLabs/mAI/tree/main/.agents/skills/pr
Command: npx skills add https://github.com/mDevsLabs/mAI --skill pr-mdevslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating cross-layer pull requests across a multi-layer codebase so server changes merge before dependent clients, reducing manual PR juggling and mis-order issues.

Core Features & Use Cases

Create and coordinate PRs for the current branch, enforcing an ordered, server-first stack across layers (server, shared libs, UI/CLI/desktop).
Automatically apply a stacked PR workflow so that changes across trunk layers can be reviewed and merged safely in the correct sequence.
Integrate with PR templates and issue linking to maintain consistency and traceability across related work.

Quick Start

Initiate a stacked PR for your current branch to ensure the server-layer PR lands first.

Frequently Asked Questions about pr

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

FAQPage Schema

How do I automate stacked pull requests for cross-layer code changes?▼

You can automate stacked pull requests by applying a workflow that creates and coordinates PRs for your current branch, enforcing a server-first merge order. This reduces manual PR juggling and prevents mis-ordering when changes span multiple repository layers.

What is a server-first merge order in a stacked PR workflow?▼

A server-first merge order ensures that server-layer pull requests are reviewed and merged before dependent clients like desktop, CLI, or UI. This ordered stack guarantees changes across trunk layers integrate safely and sequentially.

Do I need GitHub CLI to create stacked PRs across repository layers?▼

Yes, you need GitHub CLI to create stacked PRs across repository layers. The workflow relies on GitHub CLI to manage branch stacks, enforce the merge sequence, and support canary-based workflows for safe deployment.

Can I link issues and use PR templates with a stacked pull request workflow?▼

Yes, you can link issues and use PR templates with a stacked pull request workflow. Integrating issue linking and PR templates maintains consistency and traceability across related work when coordinating multiple dependent pull requests.

When should I use a stacked PR workflow for branch management?▼

Use a stacked PR workflow when a change touches multiple layers like server, shared libs, desktop, CLI, or UI. It is necessary when these cross-layer changes must be reviewed and merged in a specific, dependent order to avoid breaking clients.