Split oversized pull requests into chained PR slices with dependency diagrams.
npx skills add https://github.com/kurojs/EnderDots --skill chained-pr-kurojs
Please help me install this Agent Skill. Skill: chained-pr Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/chained-pr Command: npx skills add https://github.com/kurojs/EnderDots --skill chained-pr-kurojs
It prevents reviewer overload and stalled merges by breaking large pull requests into smaller chained PRs that keep each review focused and time-bounded.
size:exception.Ask the AI to generate a chained-pr plan that splits your PR exceeding 400 changed lines into reviewable slices using a feature-branch chain with a draft tracker, including PR order, dependency diagram, and a verification plan.
High-intent search queries and answers about installing and using this skill.
To split a large pull request, you break it into chained PR slices with explicit dependency context. This enforces a changed-lines budget and applies strict branch rules to keep each review focused and under 60 minutes.
Use stacked PRs to main for sequential landability, or a feature branch chain with a draft tracker for integration-heavy work. Choosing the right chained strategy keeps diffs clean and ensures each child PR lands safely.
A 400-line limit is a strong guardrail for code review before splitting a GitHub pull request. Exceeding this changed-lines budget requires a size exception from a maintainer to prevent reviewer overload and stalled merges.
When creating chained pull requests, you must generate a dependency diagram marking the current PR with 📍. This explicit dependency context tracks parent-child relationships and treats polluted diffs as base bugs to be retargeted.
Yes, a chained PR strategy works for integration-heavy feature work by utilizing a tracker branch. This approach maintains a clean diff and dependency hygiene while keeping each deliverable isolated within strict review boundaries.
Pull requests get stalled during code review because oversized diffs cause reviewer overload. Breaking large changes into chained PR slices with a 400-line limit keeps each review focused, time-bounded, and easier to merge.
tillysosoIdentify high-confidence issues in local code changes and diffs.
TTAWDTTAutomate GitHub PR and code-review workflows using the gh CLI.
mokekuma-gitAutomate Git commits with generated messages and branch validation.
klaidliadonCoordinate pull request authoring, review, and merge readiness with gated pipelines.