subissue-orchestration_skill

This skill helps you manage complex GitHub issues by creating and linking subissues to a parent, with native API and markdown fallback.

TypeScript

4

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill constellos/claude-code --skill subissue-orchestration

SKILL.md4.8 KB

Overview

This skill orchestrates creation and management of hierarchical GitHub issues, enabling teams to break epics into tracked subissues. It prefers GitHub's native sub-issues API for proper parent-child links and Projects integration, with a markdown checklist fallback for compatibility. It also coordinates PRs so merges automatically close their associated subissues.

How this skill works

The skill creates child issues and links them to a parent using GitHub’s native sub-issues API when available. If native sub-issues are not supported, it generates and syncs a markdown checklist in the parent issue to represent subtasks. It also injects automatic PR-to-subissue links (e.g., "Closes #X") so merging a PR closes the related subissue and keeps traceability from task → issue → PR → merge.

When to use it

Breaking an epic into implementation tasks
Splitting a monolithic issue into smaller, trackable subtasks
Tracking progress across multiple contributors with clear parent-child relationships
Automatically linking PRs to tasks so merges close subissues
Maintaining cross-repository subtasks or nested work items

Best practices

Prefer native sub-issues when the API is available for full UI and Projects integration
Include "**Parent Issue:** #N" in subissue bodies to ensure compatibility with checklist fallback
Keep subissues small and focused—one actionable unit per subissue
Use consistent labels (epic/task) to enable filtering and grouping
Rely on the stacked PR workflow to automatically add "Closes #subissue" lines to PR bodies

Example use cases

Create an authentication epic and spawn subtasks for OAuth, email auth, password reset, and 2FA, then auto-sync checklist states
Bulk-create a set of task issues from a task list, link them as native sub-issues, and update the parent checklist or relationships
When a subagent finishes a change, generate a PR that includes a "Closes #subissue" link so merging closes the subissue automatically
Convert an existing checklist in a parent issue into native sub-issues when the repository gains native sub-issues support

FAQ

The skill falls back to a markdown checklist in the parent issue and provides utilities to generate, update, and sync checklist items and states.

How are PRs tied to subissues?

The workflow injects "Closes #subissueNumber" into PR bodies (looked up from the task-to-subissue mapping) so merges automatically close the linked subissue.