batch-issues

Group GitHub issues into an epic by automatically minting a parent tracking issue and linking child issues as native sub-issues. This ensures complex multi-part features are tracked as a cohesive unit with shared metadata and dependency chains.

Manage dependencies across GitHub issues by configuring dependency chains within a parent epic batch. This establishes logical execution order for child tasks, ensuring related implementation steps are executed sequentially.

Yes, you need the GitHub CLI (gh) to create issue batches. The skill requires gh to perform authenticated API operations for issue creation, sub-issue linking, and metadata modification within your repository.

Yes, you can synchronize milestones and labels across multiple GitHub issues at once. The skill applies shared milestones, labels, and assignees across the entire batch to ensure consistent metadata throughout the epic.

Use an epic batch to solve the fragmentation of small, related tasks. Grouping individual issues into a single durable parent issue ensures complex features are implemented cohesively rather than tracked as disconnected items.

Yes, you can assign a single developer to a batch of GitHub issues. When grouping tasks into an epic, the skill assigns the entire batch to one developer while setting up the necessary dependency order for implementation.