skills.rest
AD-Paladins
AD-PaladinsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

chained-pr

Splits oversized pull requests into chained or stacked PRs with dependency diagrams and review budgets.

Updated Jul 10, 2026
Search Tags:#code review#pull request#git workflow#github#branching#stacked prs#review budget
One-click install
npx skills add https://github.com/AD-Paladins/beaconator-web --skill chained-pr-ad-paladins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chained-pr
Source: https://github.com/AD-Paladins/beaconator-web/tree/main/.config/opencode/skills/chained-pr
Command: npx skills add https://github.com/AD-Paladins/beaconator-web --skill chained-pr-ad-paladins

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large pull requests over 400 changed lines overwhelm reviewers, slow down merges, and hide defects. This Skill enforces a reviewable PR size by splitting big changes into ordered, independently verifiable chained PRs. ## Core Features & Use Cases - Size-Based Splitting: Detects PRs exceeding 400 changed lines and splits them into focused work units reviewable in under 60 minutes. - Two Chain Strategies: Supports Stacked PRs to main for independently shippable slices, and Feature Branch Chain with a draft tracker PR when the feature must integrate before merging. - Chain Context & Dependency Diagrams: Adds a Chain Context section and a dependency diagram marking the current PR with 📍 to every child PR. - Use Case: A developer finishes a 1,200-line feature. The Skill splits it into three stacked PRs, each with its own tests, clean diff, review budget, and rollback scope, so reviewers approve each slice quickly. ## Quick Start Ask the assistant to split this oversized pull request into chained PRs under 400 lines each with a dependency diagram.

Frequently Asked Questions about chained-pr

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

FAQPage Schema
How do I split a large pull request into smaller PRs?▼

Identify independent work units in the diff, then create one branch and PR per unit. Use stacked PRs to main when each slice can ship independently, or a feature branch chain with a draft tracker PR when the feature must integrate before merging.

What is the difference between stacked PRs and a feature branch chain?▼

Stacked PRs target main directly and each slice can land in order, allowing partial behavior to ship. A feature branch chain uses a draft tracker PR where children target parent branches, so nothing lands on main until the whole chain completes.

When should a pull request be split by line count?▼

Split any PR exceeding 400 changed lines unless a maintainer explicitly grants a size:exception. Each resulting PR should stay reviewable in about 60 minutes and contain one deliverable work unit with its own tests and docs.

How do I fix a polluted diff in a stacked PR?▼

A polluted diff is treated as a base bug. Retarget or rebase the child PR onto its immediate parent branch until GitHub shows only the current work unit, then verify CI passes for that branch alone.

Can generated or migration diffs be split into chained PRs?▼

Generated, vendor, or migration diffs that cannot split cleanly should not be forced into a chain. Instead, ask a maintainer for a size:exception and document the rationale in the PR output.

Related Skills

Explore More Software Engineering Skills→
mastra-aimastra-ai
27.6k

pr-splitter

Splits large pull requests into smaller reviewable stacked or parallel PRs using git.

Official
Intermediate
albersgalbersg

chained-pr

Splits oversized pull requests into chained review slices with dependency diagrams and branch strategies.

Community
Intermediate
douglancedouglance
4

incremental-implementation

Splits multi-file code changes into independently tested and verifiable implementation slices.

Community
Intermediate
wahidyankfwahidyankf
3

repo-practicing-trunk-based-development

Enforce small, frequent commits to the main branch for Trunk Based Development workflows.

Community
Advanced