gentle-ai-chained-pr

1## Activation Contract
2 
3Load this skill when a planned PR may exceed **400 changed lines**, SDD forecasts `400-line budget risk: High` or `Chained PRs recommended: Yes`, or the user asks for chained/stacked PRs, review slices, or reviewer-load control.
4 
5## Hard Rules
6 
7- Split PRs over **400 changed lines** unless a maintainer explicitly accepts `size:exception`.
8- Keep each PR reviewable in about **≤60 minutes**.
9- Use one deliverable work unit per PR; keep tests/docs with the unit they verify.
10- State start, end, prior dependencies, follow-up work, and out-of-scope items in every chained PR.
11- Every child PR must include a dependency diagram marking the current PR with `📍`.
12- In Feature Branch Chain, create a draft/no-merge tracker PR; child PR #1 targets the tracker branch, later children target the immediate parent branch.
13- Treat polluted diffs as base bugs: retarget or rebase until only the current work unit appears.
14- Do not mix chain strategies after the user chooses one.
15 
16## Decision Gates
17 
18| Condition | Action |
19|---|---|
20| PR ≤400 changed lines and focused | Keep single PR. |
21| PR >400, each slice can land independently | Use Stacked PRs to main. |
22| PR >400, feature must integrate before main | Use Feature Branch Chain with tracker. |
23| Generated/vendor/migration diff cannot split cleanly | Ask maintainer for `size:exception`. |
24| SDD provides `delivery_strategy` | Follow it before apply/PR creation. |
25 
26## Execution Steps
27…