chained-pr

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

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill chained-pr-zmynxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chained-pr
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/chained-pr
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill chained-pr-zmynxx

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 structured workflow that splits oversized changes into chained or stacked PRs so each slice stays reviewable in under an hour. ## Core Features & Use Cases - Size-Based Decision Gates: Automatically routes PRs over 400 changed lines into either Stacked PRs to main or a Feature Branch Chain with a draft tracker PR. - Chain Context Templates: Adds a standardized Chain Context section with dependency diagrams, review budgets, and scope boundaries to every child PR without replacing the repo PR template. - Diff Hygiene Enforcement: Treats polluted diffs as base bugs, requiring retargeting or rebasing until each PR shows only its own work unit. - Use Case: A developer finishes a 1,200-line feature. The Skill splits it into three child PRs targeting a tracker branch, each with a dependency diagram marking its position, so reviewers approve focused slices in order. ## 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?▼

Estimate changed lines and identify independent work units, then choose a chain strategy. Use stacked PRs to main when slices land 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 so each slice ships in order, while a feature branch chain accumulates work on a tracker branch that merges only after all child PRs complete. Stacking is simpler; chaining avoids partial behavior landing on main.

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

Split any PR exceeding 400 changed lines unless a maintainer grants a size:exception. Each resulting PR should be 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 pull request?▼

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

Can generated or vendor code avoid the 400-line PR limit?▼

Generated, vendor, or migration diffs that cannot split cleanly may request a maintainer-approved size:exception. Without that explicit exception, the 400-line split rule still applies.