Split GitHub Issue

This documentation was generated with the assistance of AI. Please report any inaccuracies.

Turn one oversized issue into a root issue plus small, self-sufficient sub-issues ordered by dependency.

Purpose

iru-split-github-issue judges size from signals (many requirements, several independently deliverable capabilities, several areas touched, estimated difficulty hard or above), proposes slices that each own a subset of the requirements and acceptance criteria, computes Blocked by relations and parallel groups (same group means independent), reviews each sub-issue draft with Review GitHub Issue, and creates the root issue, a milestone linking it (reusing an existing milestone with the same title), the sub-issues and GitHub’s sub-issue links. Steps 1 to 5 are read-only: nothing is created, edited or linked before the explicit confirmation in Step 6. An existing issue stays the root and its original text is preserved. It stops on non-GitHub hosts.

Purpose group

Ticket Intake

Plugin

Shipped by the iru-core plugin of the ai-catalog marketplace (install with /plugin install iru-core@ai-catalog; see Plugins).

Invocation

/iru-split-github-issue <issue-number>
/iru-split-github-issue draft:<path>
/iru-split-github-issue <issue-number> force: yes

Inputs

Argument Required Description Default

Argument	Required	Description	Default
`issue-number`	One of the two	An existing issue, which stays the root.	Asked if neither form is given.
`draft:<path>`	One of the two	A not-yet-created draft file; the root is created from it.	Asked if neither form is given.
`force`	No	`yes` skips the size assessment.	`no`
`label`	No	Label for the root and sub-issues (`documentation`-kind sub-issues use `documentation` when it exists); ignored if it is not in the repository’s label list. Passed by Draft GitHub Issue.	An existing root’s own labels; none for a draft

issue-number

One of the two

An existing issue, which stays the root.

Asked if neither form is given.

draft:<path>

One of the two

A not-yet-created draft file; the root is created from it.

Asked if neither form is given.

force

yes skips the size assessment.

no

label

Label for the root and sub-issues (documentation-kind sub-issues use documentation when it exists); ignored if it is not in the repository’s label list. Passed by Draft GitHub Issue.

An existing root’s own labels; none for a draft

Outputs

After confirmation: the root issue (new or rewritten), a milestone linking it (found by title across open and closed milestones and reused, or created), the sub-issues in dependency order, and sub-issue links (a task list fallback when the endpoint is unavailable).
A report with the milestone and issue URLs and a table of sub-issues.
If the user declines, nothing is created and the proposal is the deliverable.

Execution flow

flowchart TD A["Start"] --> B["Resolve input, GitHub check, fetch"] B --> C{Large enough\nor force?} C -- no --> Z["Stop: not large enough"] C -- yes --> D["Propose sub-issues"] D --> E["Compute dependencies and groups"] E --> F["Review each draft\n(iru-review-github-issue)"] F --> G{User confirms?} G -- adjust --> D G -- no --> Y["Stop: proposal is the deliverable"] G -- yes --> H["Look up milestone, create root,\nmilestone, sub-issues, links"] H --> I["Report"]

Dependencies

Invokes

Review GitHub Issue - Step 5, to review each proposed sub-issue draft.

Invoked by

Draft GitHub Issue - Step 8, when the drafted issue is too large.

Otherwise a top-level entry point, run directly by a person.

Related agents

None; iru-split-github-issue does not spawn any agent.

Source

SKILL.md on GitHub - the file this page was generated from.