gh-sub-issue

Link GitHub issues as parent-child sub-issues via the GitHub API.

3|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/codekiln/langstar --skill gh-sub-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-sub-issue
Source: https://github.com/codekiln/langstar/tree/main/.claude/skills/gh-sub-issue
Command: npx skills add https://github.com/codekiln/langstar --skill gh-sub-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies managing complex GitHub issue hierarchies and breaking down large epics into manageable sub-tasks. It links existing issues directly, preserving their numbers and history, unlike manual methods that often create fragmented records.

Core Features & Use Cases

  • Non-Destructive Linking: Link existing issues as sub-tasks without closing or recreating them, maintaining full issue history and references.
  • Hierarchical Creation: Create new issues with parent relationships established from the start, streamlining the breakdown process.
  • Use Case: Break down a large "Implement User Authentication" epic (issue #92) into smaller phases like "Design API" (issue #103) and "Implement JWT" (issue #104), ensuring they are officially linked as sub-issues in GitHub.

Quick Start

Link issue #103 as a sub-task of issue #92 in the current GitHub repository.

Frequently Asked Questions about gh-sub-issue

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

FAQPage Schema
How do I organize GitHub issues into a parent-child hierarchy?

Link existing GitHub issues as sub-issues to create hierarchical relationships. This establishes official parent-child connections through the GitHub API, preserving issue numbers, history, and enabling clear navigation across related tasks without recreating or closing issues.

Can I break down a large GitHub epic into smaller sub-tasks while keeping issue history?

Yes. Non-destructive linking preserves each issue's original number and full history. Link existing issues as sub-tasks of an epic issue, or create new issues with parent relationships established from the start, maintaining all references and audit trails.

What's the difference between linking issues as sub-issues versus closing and recreating them?

Sub-issue linking is non-destructive: original issue numbers and history remain intact, enabling coherent navigation and official parent-child relationships. Manual recreation fragments records, loses issue references, and breaks audit trails for project tracking and phase management.

How do I automate GitHub issue organization for phased development?

Use the GitHub CLI to link issues as sub-tasks of parent issues, establishing hierarchical structure for epic breakdowns and phased workflows. List, create, and remove sub-issue relationships programmatically, reducing manual project organization overhead.

Do I need special permissions to create GitHub issue hierarchies?

Sub-issue linking operates through the GitHub API and requires standard repository write access. No additional permissions are needed beyond what's required to manage issues in your GitHub repository.

Can I remove or modify sub-issue relationships after creating them?

Yes. The skill supports creating, listing, and removing sub-issue relationships. Modify hierarchies without affecting the original issues, enabling flexible project restructuring and non-destructive workflow adjustments.