batch-issues

Name: batch-issues
Availability: InStock
Author: offlinecv

Group multiple GitHub issues into a single parent epic with sub-issue links and metadata.

8|Updated May 29, 2026

Search Tags:#automation #workflow #github #epic #issue-tracking #project-management

Ready to run

npx skills add https://github.com/offlinecv/OfflineCV --skill batch-issues-offlinecv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: batch-issues
Source: https://github.com/offlinecv/OfflineCV/tree/main/.claude/skills/batch-issues
Command: npx skills add https://github.com/offlinecv/OfflineCV --skill batch-issues-offlinecv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This skill solves the fragmentation of small, related tasks by grouping them into a single, durable epic issue, ensuring that complex features can be implemented and tracked as a cohesive unit.

Core Features & Use Cases

Epic Creation: Automatically mints a parent tracking issue and links child issues as native GitHub sub-issues.
Metadata Synchronization: Applies shared milestones, labels, and assignees across the entire batch to ensure consistency.
Dependency Management: Configures dependency chains so that tasks are executed in the correct logical order.
Use Case: When a developer needs to implement a multi-part feature, this skill bundles the individual tasks into one epic, assigns them to a single developer, and sets up the necessary dependency order for implementation.

Quick Start

Use the batch-issues skill to group issues 341, 346, and 349 into a new epic titled Feature Implementation.

Frequently Asked Questions about batch-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I group GitHub issues into an epic for unified tracking?▼

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.

What's the best way to manage dependencies across multiple GitHub issues?▼

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.

Do I need the GitHub CLI to create issue batches?▼

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.

Can I synchronize milestones and labels across multiple GitHub issues at once?▼

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.

Why use an epic batch instead of individual GitHub issues?▼

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.

Can I assign a single developer to a batch of GitHub issues?▼

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.