Agent skill
create-sub-issue
Create a sub-issue linked to a parent GitHub issue
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/create-sub-issue-sasamuku-dotfiles-2
SKILL.md
Create Sub-Issue
Create a sub-issue linked to a parent GitHub issue using the sub-issue API.
Arguments
- Parent issue number (e.g.,
123or#123) - Parent issue URL
- Sub-issue description (optional)
$ARGUMENTS
Process
1. Get Parent Issue Context
gh issue view <issue-number> --json number,title,body,url
Find PLANS_SYNC_MARKER comment for detailed context.
2. Create Sub-Issue
Follow create-issue guidelines with:
- REQUIRED: Start body with
Part of #{parent-issue-number} - Create focused, actionable issue
3. Link to Parent
ISSUE_URL=$(gh issue create --title "$TITLE" --body "$BODY" --label "sub-issue")
ISSUE_NUMBER=$(echo $ISSUE_URL | grep -o '[0-9]*$')
# IMPORTANT: Use .id (integer), NOT .node_id (string)
SUB_ISSUE_ID=$(gh api /repos/{owner}/{repo}/issues/$ISSUE_NUMBER --jq .id)
gh api --method POST /repos/{owner}/{repo}/issues/{parent-number}/sub_issues \
-F "sub_issue_id=$SUB_ISSUE_ID"
4. Order Multiple Sub-Issues (if creating several)
gh api --method PATCH /repos/{owner}/{repo}/issues/{parent-number}/sub_issues/priority \
--input - <<< '{"sub_issue_id": '$SUB_ISSUE_ID', "after_id": '$PREV_SUB_ISSUE_ID'}'
Body Format
Part of #{parent-issue-number}
[Template content or standard structure]
Best Practices
- Use parent issue body + PLANS_SYNC_MARKER comment for context
- Keep sub-issues focused and independently completable
- Apply consistent labels
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?