chained-pr

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

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill chained-pr-carloswilliamsr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chained-pr
Source: https://github.com/CarlosWilliamsR/SketchOS/tree/main/.config/opencode/skills/chained-pr
Command: npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill chained-pr-carloswilliamsr

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 splits oversized changes into ordered, independently reviewable chained PRs so each slice stays focused and reviewable in under an hour. ## Core Features & Use Cases - Strategy Selection: Choose between Stacked PRs to main or a Feature Branch Chain with a draft tracker PR based on whether slices can land independently. - Chain Context Blocks: Append a standardized Chain Context section with dependency diagrams, review budgets, and scope boundaries to every PR body. - Diff Hygiene Enforcement: Detect polluted diffs and retarget or rebase child PRs so each one shows only its own work unit. - Use Case: A feature branch touches 1,200 lines across core logic, shared utilities, and docs. The Skill splits it into three chained PRs, each under 400 lines, with a tracker PR coordinating final integration. ## Quick Start Ask the assistant to split this oversized pull request into chained PRs using the chained-pr strategy.

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, 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 to main.

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 contain one deliverable work unit reviewable in about 60 minutes, with its tests and docs included.

How do I fix a polluted diff in a stacked pull request?

Treat a polluted diff as a base bug: retarget or rebase the child PR onto its immediate parent branch until only the current work unit appears. After a parent merges, rebase the next PR so GitHub shows only that slice.

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.