SkillAgentSearch skills...

gentle-ai-chained-pr

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

Install / Use

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

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Category

Legal

Supported Platforms

Zed

Our assessment of gentle-ai-chained-pr

gentle-ai-chained-pr scores 83/100 on our quality scale, 64th of 103 Legal skills we index.

Its SKILL.md is 2.5 KB long, split into 6 sections and no code examples: a solid amount of guidance for an agent.

With 7,305 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 2 days ago, so gentle-ai-chained-pr is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

gentle-ai-chained-pr compared with similar skills

All 4 of these similar skills score higher than gentle-ai-chained-pr; compare them before choosing.

SkillScoreStarsUpdatedFormat
gentle-ai-chained-pr (this skill)by Gentleman-Programming837.3k2d agoSKILL.md
algorithmic-artby anthropics100177.9k5d agoSKILL.md
pptxby anthropics100177.9k5d agoSKILL.md
designby nextlevelbuilder100130.2k6d agoSKILL.md
ui-ux-pro-maxby nextlevelbuilder100130.2k6d agoSKILL.md

Frequently asked questions

How do I install gentle-ai-chained-pr?
Run npx skills add Gentleman-Programming/gentle-ai --skill gentle-ai-chained-pr. The install tabs above show the steps for each supported agent.
Which AI agents does gentle-ai-chained-pr work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is gentle-ai-chained-pr safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is gentle-ai-chained-pr still maintained?
The repository was last updated 2 days ago, so gentle-ai-chained-pr is actively maintained.

name: gentle-ai-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, 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

| 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. | | SDD provides delivery_strategy | Follow 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

Related Skills

View on GitHub
GitHub Stars7.3k
CategoryLegal
Updated2d ago
Forks799

Languages

Go

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions