gh-attach-subissue

Resolve GitHub issue node IDs and apply the addSubIssue mutation.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/japurcell/skills --skill gh-attach-subissue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-attach-subissue
Source: https://github.com/japurcell/skills/tree/main/skills/gh-attach-subissue
Command: npx skills add https://github.com/japurcell/skills --skill gh-attach-subissue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables true GitHub sub-issue relationships by resolving issue node IDs and invoking the GraphQL addSubIssue mutation, turning references into a real hierarchical link rather than a simple text note.

Core Features & Use Cases

  • Real sub-issue linking: Resolve parent and child issues to GraphQL node IDs and attach them with addSubIssue.
  • Safe, shell-friendly commands: Inline IDs into the mutation text and avoid shell-unsafe GraphQL variable usage.
  • Usage scenarios: Build an issue tree, attach a task under a parent, or link tracker issues with real hierarchy.

Quick Start

Provide the parent and child issue references, then generate and run a GraphQL mutation that inlines the resolved IDs to create the sub-issue relationship.

Frequently Asked Questions about gh-attach-subissue

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

FAQPage Schema
How do I create a real GitHub sub-issue relationship using GraphQL?

Create a GitHub sub-issue relationship by resolving both issues to their GraphQL node IDs and applying the addSubIssue mutation, which establishes a real parent-child hierarchy instead of a plain text reference.

Can I link GitHub sub-issues from owner/repo#issue formats or full URLs?

Yes, you can attach sub-issues by providing references in owner/repo#parent and owner/repo#child formats, or by using full GitHub issue URLs as inputs to resolve the necessary node IDs.

Why does the GraphQL addSubIssue mutation inline node IDs instead of using variables?

Inlining resolved node IDs directly into the mutation text avoids shell-unsafe GraphQL variable usage, keeping the generated shell command safe and executable while maintaining the correct parent-child link.

What is the difference between a real GitHub sub-issue and a text reference?

A real GitHub sub-issue uses the GraphQL addSubIssue mutation to create a true hierarchical parent-child link, whereas a text reference is simply a note in the issue body with no structural relationship.

Does the sub-issue attachment process verify that both GitHub issues exist?

Yes, the process verifies that both the parent and child GitHub issues exist and successfully resolves their GraphQL node IDs before proceeding to execute the addSubIssue mutation.

What's the best way to build an issue tree with parent-child hierarchy on GitHub?

Build an issue tree by resolving parent and child issue node IDs and applying the GraphQL addSubIssue mutation to each pair, creating real hierarchical links suitable for tracking tasks and sub-tasks.