chained-pr

by Gentleman-Programming7.8k

Developer Tools

Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.

Install

The skill file stays in the publisher's repository.

Paste the copied command in a terminal. It installs this SKILL.md into that agent.

npx skills add Gentleman-Programming/gentle-ai --skill chained-pr -a cursor -y

Download skill internal/assets/skills/chained-pr/SKILL.md on GitHub

Related skills

View all

R
reaReverse engineer anything with agents, from app behavior down to native binaries.
R
rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
R
rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

Questions

How do I install chained-pr?: Download internal/assets/skills/chained-pr/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does chained-pr live?: The publisher keeps it at https://github.com/Gentleman-Programming/gentle-ai.
Which agents can use chained-pr?: Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.

name: chained-pr description: "Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus." license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"

Activation Contract

Load this skill when a planned PR may exceed 400 changed lines, an ODD feature's forecast or running authored changed-line count from work-unit commits exceeds about 400, or the user asks for chained/stacked PRs, review slices, or reviewer-load control.

Hard Rules

Split PRs over 400 changed lines unless a maintainer explicitly accepts size:exception.
The budget constrains how work is sliced, never the code itself. Never delete comments, blank lines, docs, or tests, and never compress or restyle code, to fit under the budget.

Condition	Action
PR ≤400 changed lines and focused	Keep single PR.
PR >400, each slice can land independently	Use Stacked PRs to main.
PR >400, feature must integrate before main	Use Feature Branch Chain with tracker.
Generated/vendor/migration diff cannot split cleanly	Ask maintainer for `size:exception`.
No cohesive split fits the budget after one slicing pass	Stop; deliver the best split, report the overage and why it cannot shrink further, and recommend `size:exception`.
ODD provides `delivery_strategy` and `chain_strategy`	Follow them before the next work-unit commit or PR creation.

chained-pr

Install

Related skills

Questions

name: chained-pr description: "Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus." license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"

Activation Contract

Hard Rules

Decision Gates

Execution Steps

Output Contract

References