무료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.

Gentleman-Programming/gentle-ai

설치 방법 보기

이럴 때 유용합니다

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(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

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.

Execution Steps

Estimate changed lines and identify independent work units.
Ask for a chain strategy when none is cached and the budget is exceeded.
Create branches/PRs using the chosen strategy only.
Add Chain Context to each PR without replacing the repo PR template.
Verify each PR independently: CI/tests/docs/manual checks, rollback scope, and clean diff.
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

references/chaining-details.md — strategy diagrams, PR body section, branch commands, and reviewer guidance.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

같은 저장소의 스킬

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-ai7.9천2026년 10월 18일 업데이트

cognitive-doc-design

무료

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-ai7.9천2026년 10월 18일 업데이트

comment-writer

무료

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-ai7.9천2026년 10월 18일 업데이트

gentle-ai-bench

무료

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-ai7.9천2026년 10월 18일 업데이트

gentle-ai-branch-pr

무료

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-ai7.9천2026년 10월 18일 업데이트

gentle-ai-chained-pr

무료

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-ai7.9천2026년 10월 18일 업데이트

Gentleman-Programming의 스킬 모두 보기

이 스킬의 문제 신고

설치

명령으로 설치

npx skills add https://github.com/Gentleman-Programming/gentle-ai --skill chained-pr

터미널에 붙여 넣고 실행합니다(Node.js 필요). Claude Code, Codex 등 설치할 에이전트를 고를 수 있습니다.

에이전트에게 부탁하기

다음 Agent Skill을 설치해 주세요.
https://github.com/Gentleman-Programming/gentle-ai/tree/main/internal/assets/skills/chained-pr

먼저 SKILL.md와 첨부 파일의 내용을 확인해 수상한 처리(외부 전송, 인증 정보 읽기 등)가 없는지 확인한 뒤 Claude Code는 ~/.claude/skills/chained-pr/, Codex는 ~/.agents/skills/chained-pr/ 에 배치해 주세요.

이 문장을 그대로 Claude Code나 Codex에 보내면 내용을 확인한 뒤 설치해 줍니다.

GitHub에서 소스 보기

저장소: Gentleman-Programming/gentle-ai
스타: 7,856
포크: 845
카테고리: 개발
라이선스: MIT
원문 언어: 영어
최종 업데이트: 2026년 10월 18일

스킬은 에이전트를 위한 지시와 스크립트의 묶음입니다. cccskills는 내용의 안전성을 보증하지 않습니다. 설치하기 전에 내용을 확인하세요.