GitHub Issue Breakdown FAQs

Question 1

Can I see what issues will be created before they are actually made?

Accepted Answer

Absolutely. The skill includes an interactive dry-run mode and a preview feature. It will show you exactly which tasks were parsed and what the proposed sub-issues will look like, asking for your confirmation before performing any write operations to your repository.

Question 2

Does it support metadata like labels and assignees?

Accepted Answer

Yes. The skill features automatic metadata inheritance, meaning newly created sub-issues can automatically inherit labels and assignees from the parent issue, maintaining consistency across your project hierarchy.

Question 3

What does the GitHub Issue Breakdown skill do?

Accepted Answer

This skill automates the process of converting markdown task lists (checklists, bullet points, or numbered lists) within a GitHub issue description into official GitHub sub-issues. It utilizes the GitHub GraphQL API to establish native parent-child relationships, ensuring they appear correctly in the GitHub project UI.

Question 4

How does it improve my GitHub workflow?

Accepted Answer

It eliminates the manual overhead of creating dozens of related issues. By automating the hierarchy, it ensures your project progress is accurately tracked in GitHub's sub-issue UI, prevents informal 'broken' links, and helps maintain a clean, organized backlog for complex features.

Question 5

When is the best time to use this skill?

Accepted Answer

The most critical time to use this skill is immediately after creating an Epic or parent issue that contains a task list. Using this skill ensures that sub-tasks are officially linked to the parent, which manual issue creation cannot easily achieve.

GitHub Issue Breakdown

GitHub Issue Breakdown

Key Features

Use Cases

Key Features

Use Cases