github-graphql-api

Link child issues to parent issues via the GitHub GraphQL API.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/takemo101/compose-workflow --skill github-graphql-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-graphql-api
Source: https://github.com/takemo101/compose-workflow/tree/main/.opencode/skill/github-graphql-api
Command: npx skills add https://github.com/takemo101/compose-workflow --skill github-graphql-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill bypasses bugs in the GitHub REST API related to sub-issue management by providing a reliable GraphQL API interface for linking issues.

Core Features & Use Cases

  • Sub-issue Creation: Programmatically link child issues to parent issues.
  • Error Handling: Gracefully handles API failures and missing Node IDs, preventing workflow stoppages.
  • Use Case: When decomposing a large task into smaller subtasks (issues), this Skill ensures they are correctly linked to the main parent issue, improving project organization and traceability.

Quick Start

Use the github-graphql-api skill to add issue 42 as a sub-issue of issue 10.

Frequently Asked Questions about github-graphql-api

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

FAQPage Schema
How do I link child issues to a parent issue in GitHub?

Linking child issues to a parent issue in GitHub is done by managing sub-issue relationships through the GraphQL API. This method programmatically connects decomposed subtasks to the main parent issue to improve project organization.

Why does creating GitHub sub-issues fail when using the REST API?

GitHub sub-issue creation often fails via the REST API due to known bugs in sub-issue management. Using the GraphQL API bypasses these REST API limitations, providing a reliable interface to successfully link child and parent issues.

Do I need the GitHub CLI to manage sub-issue relationships with GraphQL?

Yes, managing sub-issue relationships via GraphQL requires the GitHub CLI (gh) for authenticated API interactions. The CLI is necessary to retrieve Node IDs and execute the API calls for linking child issues to parent issues.

How do I handle missing Node IDs when linking GitHub sub-issues?

Missing Node IDs during GitHub sub-issue linking are handled by built-in error handling features. This gracefully manages API failures and missing identifiers, preventing workflow stoppages and ensuring reliable sub-issue creation.

What is the best way to automate GitHub sub-issue creation for project organization?

Automating GitHub sub-issue creation is best achieved by using the GraphQL API to programmatically link child issues to parent issues. This ensures decomposed tasks are accurately connected, improving project traceability and organization.