Managing GitHub Issue Hierarchies

Manage GitHub issue hierarchies via REST and GraphQL APIs.

1|Updated Jun 4, 2025
One-click install
npx skills add https://github.com/kynoptic/markdownlint-trap --skill managing-github-issue-hierarchies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Managing GitHub Issue Hierarchies
Source: https://github.com/kynoptic/markdownlint-trap/tree/main/.claude/skills/gh-issue-hierarchy
Command: npx skills add https://github.com/kynoptic/markdownlint-trap --skill managing-github-issue-hierarchies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages GitHub issue parent-child relationships (sub-issues) using REST and GraphQL APIs. Use when breaking down large work into Epics/Features/Tasks, creating work breakdown structures, converting markdown checklists to sub-issues, reordering sub-issues, or querying issue hierarchies. Handles ID confusion between REST numeric IDs and GraphQL node IDs.

Core Features & Use Cases

  • Add sub-issue to parent: REST and GraphQL options to link sub-issues
  • Remove sub-issue from parent: Detach sub-issues from a parent
  • Query hierarchy: Show the full tree of parent and sub-issues
  • Convert checklists to sub-issues: Transform checklist items into linked issues
  • Reorder sub-issues: Change positions within a parent's sub-issues
  • ID handling: Clarify REST numeric IDs vs GraphQL node IDs

Quick Start

Example: Create a parent issue and attach three sub-issues; fetch the hierarchical tree via GraphQL to verify structure.

Frequently Asked Questions about Managing GitHub Issue Hierarchies

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

FAQPage Schema
How do I break down large GitHub issues into sub-issues and hierarchies?

Breaking down large work into sub-issues creates a hierarchy of Epics, Features, and Tasks in GitHub. You can link sub-issues to parent issues using REST or GraphQL APIs, then query the complete tree structure to verify the hierarchy is correct.

Can I convert GitHub issue checklists into linked sub-issues automatically?

Yes, you can transform markdown checklist items into separate linked sub-issues. This converts inline task lists into trackable, independently managed issues within your parent issue's hierarchy.

How do I query GitHub issue hierarchies across REST and GraphQL APIs?

Query issue hierarchies using either REST or GraphQL to fetch the complete parent-child tree. GraphQL node IDs differ from REST numeric IDs, so the Skill handles ID mapping to ensure consistent querying across both APIs.

What's the difference between REST numeric IDs and GraphQL node IDs in GitHub issues?

REST returns numeric issue IDs while GraphQL uses opaque node IDs. Both reference the same issue, but querying hierarchies requires mapping between the two formats to avoid ID confusion when working across API styles.

How do I reorder or move sub-issues between parent issues in GitHub?

Reorder sub-issues within a parent or move them to a different parent using the REST and GraphQL APIs. This lets you reorganize work structure after issues are created without recreating the relationships.