OpenParable
Skip to content
← Back to skills

Gentle AI Chained PR

Testing & Quality
gentle-ai-chained-pr

Gentle AI Chained PR is an Agent Skill for testing & quality published in the Gentleman-Programming/gentle-ai repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Gentleman-Programming/gentle-ai/blob/HEAD/skills/chained-pr/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gentle-ai-chained-pr, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Activation Contract

Load 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.

Hard Rules

  • Split PRs over 400 changed lines unless a maintainer explicitly accepts size:exception.
  • Keep each PR reviewable in about ≤60 minutes.
  • Use one deliverable work unit per PR; keep tests/docs with the unit they verify.
  • State start, end, prior dependencies, follow-up work, and out-of-scope items in every chained PR.
  • Every child PR must include a dependency diagram marking the current PR with 📍.
  • 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.
  • Treat polluted diffs as base bugs: retarget or rebase until only the current work unit appears.
  • Do not mix chain strategies after the user chooses one.

Decision Gates

ConditionAction
PR ≤400 changed lines and focusedKeep single PR.
PR >400, each slice can land independentlyUse Stacked PRs to main.
PR >400, feature must integrate before mainUse Feature Branch Chain with tracker.
Generated/vendor/migration diff cannot split cleanlyAsk maintainer for size:exception.
SDD provides delivery_strategyFollow it before apply/PR creation.

Execution Steps

  1. Estimate changed lines and identify independent work units.
  2. Ask for a chain strategy when none is cached and the budget is exceeded.
  3. Create branches/PRs using the chosen strategy only.
  4. Add Chain Context to each PR without replacing the repo PR template.
  5. Verify each PR independently: CI/tests/docs/manual checks, rollback scope, and clean diff.
  6. Keep tracker PR draft/no-merge until all child PRs are reviewed and integrated.

Output Contract

Return the chosen strategy, PR order, current PR boundary, dependency diagram, review budget (additions + deletions), verification plan, and any size:exception rationale.

References