Menü
Link GitHub issues in parent-child (sub-issue) relationships using GraphQL
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | add-sub-issue |
| description | Link GitHub issues in parent-child (sub-issue) relationships using GraphQL |
| disable-model-invocation | true |
Create parent-child relationships between GitHub issues.
Link issues in a hierarchical structure using GitHub's sub-issues feature.
Sub-issues require the GraphQL API with a feature flag.
First, get the internal IDs for both issues:
# Get parent issue ID
PARENT_ID=$(gh issue view {parent_number} --json id --jq ".id")
echo "Parent ID: $PARENT_ID"
# Get child issue ID
CHILD_ID=$(gh issue view {child_number} --json id --jq ".id")
echo "Child ID: $CHILD_ID"
gh api graphql \
-H "GraphQL-Features: sub_issues" \
-f query='
mutation($parentId: ID!, $childId: ID!) {
addSubIssue(input: { issueId: $parentId, subIssueId: $childId }) {
issue { title number }
subIssue { title number }
}
}
' \
-f parentId="$PARENT_ID" \
-f childId="$CHILD_ID"
gh api graphql \
-H "GraphQL-Features: sub_issues" \
-f query='
mutation($parentId: ID!, $childId: ID!) {
removeSubIssue(input: { issueId: $parentId, subIssueId: $childId }) {
issue { title }
subIssue { title }
}
}
' \
-f parentId="$PARENT_ID" \
-f childId="$CHILD_ID"
PARENT_ID=$(gh issue view {parent_number} --json id --jq ".id")
gh api graphql \
-H "GraphQL-Features: sub_issues" \
-f query='
query($id: ID!) {
node(id: $id) {
... on Issue {
title
number
subIssues(first: 50) {
nodes {
number
title
state
}
}
}
}
}
' \
-f id="$PARENT_ID"
create-issue
skill (which follows github-conventions for titles/labels/milestones).addSubIssue mutation above.Auth engine rules for QAuth. Use when working with CredentialProvider implementations, token claim generation, the provider registry, or the federation layer. Enforces the pluggable provider pattern and correct token claim behaviour.
OAuth 2.1 / OIDC rules for QAuth. Use when working with authorization endpoints, token flows, PKCE, JWKS, OIDC discovery, or spec compliance (RFC 9700, OIDC Core 1.0). Covers endpoint behaviour, email claim rules, and token security.
Database schema rules for QAuth. Use when working with the identity model, Drizzle ORM, migrations, repositories, or claim resolution. Reflects the CURRENT shipped schema — the identifier-abstraction model (ADR-002, IMPLEMENTED via Epic
Add a GitHub issue to a project board using gh project item-add
Create a new GitHub issue following QAuth project conventions using gh issue create
Create a pull request following QAuth conventions with gh pr create