skills.rest
mrp4sten
mrp4stenCOMMUNITY
Explore all skills by this author →
GitHub

chained-pr

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

3|Updated Apr 5, 2023
Search Tags:#workflow#templates#github#branch-management#pull-request#chain#stacked-pr
One-click install
npx skills add https://github.com/mrp4sten/.dotfiles --skill chained-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chained-pr
Source: https://github.com/mrp4sten/.dotfiles/tree/main/development/IA/opencode/skill/chained-pr
Command: npx skills add https://github.com/mrp4sten/.dotfiles --skill chained-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chained PR workflows help teams break large features into smaller, reviewable PRs that merge into a feature branch, reducing risk and enabling parallel work.

Core Features & Use Cases

  • Supports chained PRs where sub-tasks merge to a feature branch, and a final Main PR merges to master.
  • Provides templates and guidance for consistent PR structure, base/merge rules, and dependency tracking.
  • Suits scenarios with API/UI work, parallel development, and staged release plans.

Quick Start

Create a feature branch from master, then open sub-task branches from that feature branch and publish PRs targeting the feature branch using the provided templates.

Frequently Asked Questions about chained-pr

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

FAQPage Schema
What is a chained PR workflow for large feature development?▼

A chained PR workflow breaks large features into smaller, reviewable pull requests that merge into a feature branch, reducing risk and enabling parallel work before a final main PR merges to master.

How do I set up stacked PRs in GitHub for sub-task branches?▼

To set up stacked PRs, create a feature branch from master, then open sub-task branches from that feature branch and publish pull requests targeting the feature branch using provided templates.

Can I use chained pull requests for parallel API and UI development?▼

Yes, chained pull requests suit scenarios with parallel API and UI development, staged release plans, and dependency tracking, allowing teams to review sub-tasks independently before merging to master.

What's the best way to track dependencies across stacked pull requests?▼

The best way to track dependencies across stacked pull requests is using workflow templates that enforce base-branch rules and dependency tracking, ensuring sub-task PRs merge in the correct order.

Do I need specific GitHub branch management rules for chained PRs?▼

Yes, chained PRs require specific base-branch rules to ensure sub-task branches target the feature branch rather than master, maintaining the stack structure until the final main PR is ready.

Related Skills

Explore More Software Engineering Skills→
SuniljitSuniljit

create-pr

Analyze branch diffs and create GitHub Pull Requests via gh CLI.

Community
Intermediate
haleyrchaleyrc
2

feature-merge

Squash merge feature branch commits into main with a Conventional Commit message.

Community
Intermediate
AustinZ21AustinZ21
4

speckit-taskstoissues

Convert dependency-ordered spec-kit tasks into GitHub issues.

Community
Intermediate
bobmatnycbobmatnyc
3

stacked-prs

Create and coordinate stacked pull requests with sequential branch basing.

Community
Intermediate