GitHub Issue & Sub-Issue Governance

When to Use This Skill

Use this skill when:

• Deciding whether a new initiative warrants an Epic, a Standalone Feature/Bug, or a Child Sub-Issue
• Decomposing multi-PR roadmaps into structured parent-child issue hierarchies
• Posting status or progress reports to GitHub issues without spamming tickets with repetitive comments
• Safely transmitting multi-line markdown with code blocks, backticks, or tables via GitHub CLI (gh)
• Preventing shell-stripping bugs and raw \n\n escape artifacts in public issue bodies

Trigger keywords: github issue, sub-issue, epic, ticket spam, issue template, gh issue, comment flooding, markdown corruption, gh sub-issue, in-place update.

Recommendation First

Three hard defaults eliminate ticket clutter and markdown corruption: