chained-pr

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

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/albersg/dotfiles --skill chained-pr-albersg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chained-pr
Source: https://github.com/albersg/dotfiles/tree/main/dotfiles-opencode/.opencode/skills/chained-pr
Command: npx skills add https://github.com/albersg/dotfiles --skill chained-pr-albersg

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 breaks oversized changes into focused, chained PRs that keep each review under a manageable budget while preserving integration order. ## Core Features & Use Cases - Strategy Selection: Chooses between Stacked PRs to main and Feature Branch Chain with a draft tracker PR based on whether slices can land independently. - Chain Context Blocks: Adds dependency diagrams, position markers, review budgets, and scope boundaries to every child PR without replacing the repo PR template. - Diff Hygiene Enforcement: Detects polluted diffs and requires retargeting or rebasing so each PR shows only its own work unit. - Use Case: A feature branch contains 1,200 changed lines. The Skill splits it into three child PRs targeting each other in sequence, each under 400 lines, with a draft tracker PR holding integration until all slices are reviewed. ## Quick Start Ask the assistant to split this oversized pull request into chained PRs using the chained-pr strategy and generate the dependency diagram for each slice.

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 PR per unit using either stacked PRs to main or a feature branch chain. Each PR should stay under 400 changed lines and include a dependency diagram marking its position in the chain.

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

Stacked PRs target main directly and land independently in order, while a feature branch chain uses a draft tracker PR that accumulates all child PRs before merging to main. Use stacking when slices ship independently and chaining when the feature must integrate first.

When should a pull request be split into chained PRs?▼

Split when a PR exceeds 400 changed lines or cannot be reviewed in about 60 minutes. Generated, vendor, or migration diffs that cannot split cleanly may instead request a maintainer-approved size:exception.

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

A polluted diff means the PR shows changes from parent branches and is treated as a branching bug. Retarget the PR base or rebase the branch onto its immediate parent until only the current work unit appears in the diff.

Can I mix stacked PRs and feature branch chain strategies?▼

No, the Skill forbids mixing chain strategies after one is chosen. Pick stacked PRs or a feature branch chain at the start and apply it consistently to every child PR in the chain.