seika139/dotfiles

Overview

This skill unlinks a sub-issue from a parent GitHub Issue using the GitHub CLI and GraphQL API. Provide the parent issue and the child (sub-issue) by URL or owner/repo#number and the skill performs the removeSubIssue mutation. It reports the titles of both issues after the unlink operation.

How this skill works

The skill uses gh api graphql to fetch the GraphQL Node IDs for the parent and child issues. It then calls the removeSubIssue mutation with those IDs to remove the sub-issue relation. Finally, it reads the mutation response and returns the parent and sub-issue titles to confirm success.

When to use it

• You need to remove a sub-issue relation without deleting either issue.
• Cleaning up incorrect or outdated sub-issue links in a repository.
• When reorganizing issue hierarchy or moving work out of a parent issue.
• Automating maintenance tasks that manage issue relationships via scripts.

Best practices

• Ensure gh CLI is installed and authenticated with access to the target repository.
• Supply issues in owner/repo#number or full GitHub URL format to avoid ambiguity.
• Check that the parent-child link exists before running the unlink to reduce errors.
• Run the Node ID fetch steps manually if you need to inspect outputs for debugging.
• Handle API errors and permission issues in automation to surface clear messages.

Example use cases

• Remove a mistakenly linked sub-issue after splitting a task into separate work items.
• Clean up project board relationships when reclassifying a child issue as independent work.
• Automate unlinking as part of a larger script that migrates tasks between milestones.
• Undo a bulk operation that unintentionally created sub-issue links.