github-issue-relationships

Link GitHub issues with dependencies and epics using GraphQL mutations.

Updated Mar 19, 2026

Search Tags:#github #dependencies #graphql #epics #issues #relationships #workflows

Ready to run

npx skills add https://github.com/drdanmaggs/rocket-fuel --skill github-issue-relationships

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-issue-relationships
Source: https://github.com/drdanmaggs/rocket-fuel/tree/main/internal/plugin/skills/github-issue-relationships
Command: npx skills add https://github.com/drdanmaggs/rocket-fuel --skill github-issue-relationships

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

GitHub issue relationships help you model dependencies and hierarchies between issues and epics, ensuring work proceeds in the intended order and structure.

Core Features & Use Cases

Manage dependencies (blocked-by / blocking) to enforce sequencing between issues.
Create and maintain parent-child (epic and sub-issues) hierarchies for better organization.
Interpret and apply relationship signals when linking issues, replacing ad-hoc notes with actionable links.

Quick Start

Link two issues to establish a dependency or add a parent-child relationship using GraphQL-based mutations.

Frequently Asked Questions about github-issue-relationships

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

FAQPage Schema

How do I link GitHub issues to create dependencies and parent-child hierarchies?▼

You link GitHub issues by using GraphQL-based mutations to establish dependency sequencing with blocked-by or blocking terminology, and structure parent-child epic and sub-issue relationships for organized workflows.

Can I enforce workflow sequencing between GitHub issues using standard relationship terminology?▼

Yes, enforcing workflow sequencing is possible by applying standard relationship terminology like blocked-by and blocking across multiple GitHub issues to ensure work proceeds in the intended order.

How do I manage epic and sub-issue hierarchies in GitHub without ad-hoc notes?▼

You replace ad-hoc notes with actionable links by creating and maintaining parent-child hierarchies that connect GitHub epics and sub-issues through structured relationship signals.

Does this approach to GitHub issue relationships require GraphQL mutations?▼

Yes, establishing, applying, or removing dependency and parent-child relationships between GitHub issues relies on GraphQL-based mutations to interpret and enforce the workflow structure.

What is the best way to remove an existing dependency or parent-child structure between GitHub issues?▼

The best way to remove relationships between GitHub issues is to apply GraphQL-based mutations that clear the existing blocked-by, blocking, parent, or child relationship signals.

When should I avoid using GitHub issue dependency sequencing for workflows?▼

You should avoid using GitHub issue dependency sequencing for workflows that do not require strict parent-child hierarchies or blocked-by and blocking constraints to function properly.