跳到正文
cccskills
免费在 GitHub 公开

chained-pr

Split changes exceeding 400 lines into linked pull requests with clear boundaries and dependencies. Choose a chain structure, keep tests and documentation with each work unit, and document review order, verification plans, and justified size exceptions.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

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

查看安装方法

适用场景

  • Splitting a change that exceeds 400 lines
  • Planning PRs that can merge independently
  • Coordinating a feature through a draft tracker PR
  • Documenting why a cohesive change needs a size exception

包含的文件(2)

  • SKILL.md3.1 KB
  • references/chaining-details.md3.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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.
  • Slicing is bounded: make one honest slicing pass. If no cohesive split brings every slice within budget, stop iterating, keep the best cohesive split, and report the final line count with a size:exception recommendation.
  • 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.
No cohesive split fits the budget after one slicing passStop; deliver the best split, report the overage and why it cannot shrink further, and recommend size:exception.
ODD provides delivery_strategy and chain_strategyFollow them before the next work-unit commit or 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

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

branch-pr

免费

Prepare pull requests by checking approved issue links, change-type labels, and required automated checks. Draft the repository’s PR template using observed test results, while leaving commits, pushes, PR creation, and merging under human control.

中文简介正在准备中。当前显示英语简介。

  • Preparing a branch for review
  • Drafting a PR linked to an approved issue
  • Checking required CI before declaring a PR merge-ready
Gentleman-Programming/gentle-ai78482026年10月18日 更新

Structure guides, READMEs, design documents, and pull request descriptions so readers can find answers quickly. Put outcomes first, introduce details gradually, and use examples, tables, and checklists to support understanding and review.

中文简介正在准备中。当前显示英语简介。

  • Reorganizing a long or dense README
  • Writing an onboarding guide for new contributors
  • Making a pull request's review steps clear
Gentleman-Programming/gentle-ai78482026年10月18日 更新

Draft clear, considerate comments for code reviews, issue replies, and team updates. Put the actionable point first, explain technical reasons when needed, and give a concrete next step while matching the conversation’s language.

中文简介正在准备中。当前显示英语简介。

  • Requesting a code change with a clear reason
  • Replying to a contributor’s issue
  • Writing a brief asynchronous team update
Gentleman-Programming/gentle-ai78482026年10月18日 更新

Create and verify gentle-ai journeys, which are scripted sequences of product actions. Check their declarations separately from actual execution, review outdated expectations after behavior changes, and record execution results for pull requests.

中文简介正在准备中。当前显示英语简介。

  • Adding a product operation journey
  • Updating expectations after behavior changes
  • Reproducing a bench failure from CI
Gentleman-Programming/gentle-ai78482026年10月18日 更新

Prepare Gentle AI changes for review by linking approved issues, following branch and commit naming rules, and drafting pull requests with observed test results. Check change size and required automated checks before claiming readiness.

中文简介正在准备中。当前显示英语简介。

  • Preparing a branch for a fix or feature
  • Drafting a pull request linked to an approved issue
  • Organizing test results and reviewer notes
Gentleman-Programming/gentle-ai78482026年10月18日 更新

Split large code changes into linked pull requests, each with a focused scope. Organize their order, dependencies, and verification steps so reviewers can assess one unit of work at a time.

中文简介正在准备中。当前显示英语简介。

  • Splitting a pull request with more than 400 changed lines
  • Planning the review order for dependent changes
  • Integrating a feature through a shared branch
Gentleman-Programming/gentle-ai78482026年10月18日 更新

查看 Gentleman-Programming 的全部技能

报告此技能的问题