issue-split-en

Split large GitHub issues into scope-based sub-issues with user-approved drafts.

Updated May 3, 2026

Search Tags:#github issues #task planning #gh cli #spec extraction #interactive approval #issue splitting

Ready to run

npx skills add https://github.com/ousiass/dotfiles --skill issue-split-en

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-split-en
Source: https://github.com/ousiass/dotfiles/tree/main/.claude/skills/issue-split-en
Command: npx skills add https://github.com/ousiass/dotfiles --skill issue-split-en

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This Skill helps you convert a large, hard-to-implement GitHub Issue into smaller, scope-based sub-issues that are clear to work on.

Core Features & Use Cases

Interactive scope splitting: Proposes an implementation-order breakdown and iterates with approval, finer splits, merges, or modifications.
Spec-anchored sub-issue drafting: For each scope, drafts a sub-issue whose “Related Specs” embeds only the relevant spec excerpts verbatim to prevent drift.
Controlled creation and linking: Creates each approved sub-issue via the gh CLI and appends a checklist-style “Sub-issues” section back to the parent issue.

Quick Start

Ask your AI to run issue-split-en for an existing GitHub issue URL and have it propose scopes, confirm them one by one, then create and link the resulting sub-issues.

Frequently Asked Questions about issue-split-en

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I split a large GitHub issue into smaller sub-issues?▼

To split a large GitHub issue, you use an interactive scope-based approach that proposes a breakdown and iterates with your approval before creating sub-issues. This allows you to divide spec-heavy parent issues into independently implementable tasks.

How does spec extraction prevent drift when breaking down GitHub issues?▼

Spec extraction prevents drift by embedding only the relevant spec excerpts verbatim into each sub-issue's Related Specs section. This ensures the original specification details are preserved exactly during interactive issue splitting.

Do I need the gh CLI to automate GitHub issue splitting?▼

Yes, you need the gh CLI installed to automate GitHub issue splitting. The process requires the gh CLI for retrieving the parent issue and creating the approved sub-issues directly within your repository.

Can I modify the proposed scope breakdown before sub-issues are created?▼

Yes, you can modify the proposed scope breakdown before sub-issues are created. The interactive approval process allows you to request finer splits, merge scopes, or apply modifications before finalizing the sub-issue creation.

What is the best way to organize GitHub issues for parallel execution?▼

The best way to organize GitHub issues for parallel execution is scope-based splitting across environment, backend, frontend, tests, and CI. This creates independently implementable sub-issues linked back to the parent for clear task tracking.