chained-pr

Splits oversized pull requests into chained review slices under 400 changed lines.

Updated May 24, 2026
One-click install
npx skills add https://github.com/etrigan16/v0-cipher-ar --skill chained-pr-etrigan16
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chained-pr
Source: https://github.com/etrigan16/v0-cipher-ar/tree/main/.opencode/skills/chained-pr
Command: npx skills add https://github.com/etrigan16/v0-cipher-ar --skill chained-pr-etrigan16

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Large pull requests overwhelm reviewers, slow down merges, and hide defects. This Skill enforces a 400-changed-line budget by splitting oversized work into chained or stacked PRs that stay reviewable in under an hour. ## Core Features & Use Cases - Size Budget Enforcement: Splits any PR exceeding 400 changed lines unless a maintainer grants a size:exception. - Two Chain Strategies: Choose Stacked PRs to main for independently shippable slices, or a Feature Branch Chain with a draft tracker PR when the feature must integrate before landing on main. - Chain Context Metadata: Every child PR gets a dependency diagram, position marker, review budget, and rollback scope so reviewers see exactly where it fits. - Use Case: A developer finishes a 1,200-line feature. The Skill splits it into three focused PRs, each targeting its parent branch, with a tracker PR held as draft until the full chain is reviewed and merged. ## Quick Start Ask the assistant to split this oversized feature branch 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 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, and nothing lands on main until the full chain completes.

When should I use a tracker PR for chained pull requests?▼

Use a tracker PR when the feature must fully integrate before reaching main. Create it as a draft or no-merge PR, target child PR #1 at the tracker branch, and merge the tracker only after all children are reviewed.

Can a pull request exceed 400 lines without being split?▼

Only when a maintainer explicitly grants a size:exception, typically for generated code, vendor updates, or migrations that cannot split cleanly. The exception rationale must be stated in the PR output.

Why does my stacked PR show changes from the parent branch?▼

A polluted diff means the PR base is wrong, which is treated as a branching bug. Retarget or rebase the PR onto its immediate parent branch so only the current work unit appears in the diff.