skills.rest
Alountk
AlountkCOMMUNITY
Explore all skills by this author →
GitHub

chained-pr

Split oversized pull requests into chained review slices with dependency diagrams.

Updated Aug 5, 2026
Search Tags:#code review#pull request#git workflow#github#branching#stacked prs#review budget
One-click install
npx skills add https://github.com/Alountk/Bloodbowl_Project --skill chained-pr-alountk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chained-pr
Source: https://github.com/Alountk/Bloodbowl_Project/tree/main/.opencode/skills/chained-pr
Command: npx skills add https://github.com/Alountk/Bloodbowl_Project --skill chained-pr-alountk

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 review budget by splitting oversized 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 about 60 minutes. - Two chain strategies: Stacked PRs to main for independently shippable slices, or a Feature Branch Chain with a draft tracker PR when the feature must integrate before merging. - Chain Context blocks: Adds dependency diagrams, position markers, review budgets, and rollback scope to every child PR without replacing the repo PR template. - Use Case: A developer finishes a 1,200-line feature. The Skill proposes three chained PRs, creates branches targeting each parent, and keeps the tracker PR as draft until all children merge. ## Quick Start Ask the assistant to split this oversized feature branch into chained PRs under the 400-line review budget.

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 within the change, 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 be reviewable in about 60 minutes.

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

Stacked PRs target main directly and each slice can ship independently in order. A feature branch chain uses a draft tracker PR where child PRs target their parent branch, so nothing lands on main until the full chain completes.

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

Split when a PR exceeds 400 changed lines, when SDD forecasts a high 400-line budget risk, or when reviewers cannot finish a review in about 60 minutes. Generated or vendor diffs that cannot split cleanly may request a size:exception instead.

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

A polluted diff is treated as a branching 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 a large generated or migration diff avoid being split?▼

Yes, when a generated, vendor, or migration diff cannot be split cleanly, the maintainer can explicitly grant a size:exception. The exception rationale must be stated in the PR output alongside the review budget.

Related Skills

Explore More Software Engineering Skills→
Gentleman-ProgrammingGentleman-Programming
6.1k

work-unit-commits

Plans commits as reviewable work units with tests, docs, and rollback boundaries.

Official
Intermediate
open-horizon-labsopen-horizon-labs
3

oh-merge

Batch-review and merge stacked GitHub PRs in dependency order.

Official
Advanced
alasdairncalasdairnc

feature-factory

Decomposes feature specs into slices with tests and parallel subagents.

Community
Advanced
wahidyankfwahidyankf
3

repo-practicing-trunk-based-development

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

Community
Advanced