splice-issue

Decompose large GitHub issues into dependency-managed sub-issues with inherited metadata.

9|2|Updated Nov 29, 2024
One-click install
npx skills add https://github.com/bbvch-ai/aihub-core --skill splice-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: splice-issue
Source: https://github.com/bbvch-ai/aihub-core/tree/main/.claude/skills/splice-issue
Command: npx skills add https://github.com/bbvch-ai/aihub-core --skill splice-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large, multi-faceted GitHub issues are hard to track, assign, and complete because they cover too much unrelated work, leading to blocked PRs, missed acceptance criteria, and messy dependency tracking. This skill automates breaking these parent issues into small, self-contained sub-issues with correct dependency relationships so teams can work in parallel without conflicts.

Core Features & Use Cases

  • Automated Issue Decomposition: Splits a parent issue into independent, mergeable sub-issues with clear, behavior-focused acceptance criteria.
  • Dependency Management: Automatically inherits the parent's existing blocked-by and blocking relationships, and sets new dependencies between child issues to avoid redundant work.
  • Metadata Consistency: Copies labels, milestones, assignees, and project board priorities from the parent to all child issues to maintain alignment with existing workflows. Use case: For example, a large issue covering full end-to-end authentication implementation for the aihub-core stack can be split into sub-issues for SSO integration, PII filtering, and cost tracking, with correct dependency order so PII filtering is completed before SSO is merged.

Quick Start

Use the splice-issue skill to break down parent issue #123 from the bbvch-ai/aihub-core repository into linked, dependency-managed sub-issues.

Frequently Asked Questions about splice-issue

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

FAQPage Schema
How do I split large GitHub issues into linked sub-issues with dependencies?

To split a parent issue, apply automated issue decomposition to break it into independent, mergeable sub-issues with clear acceptance criteria, automatically inheriting parent metadata and setting correct dependency relationships.

Why does issue dependency tracking break down on multi-workstream GitHub projects?

Issue dependency tracking breaks down because large parent issues cover overlapping scope, leading to blocked pull requests and messy graphs. Splitting issues into self-contained sub-issues with inherited blocked-by relationships solves this.

Can I automatically inherit labels and milestones when breaking down GitHub issues?

Yes, you can automatically inherit labels, milestones, assignees, and project board priorities from the parent issue to all child issues, ensuring metadata consistency and maintaining alignment with existing development workflows.

What's the best way to manage sub-issues for parallel development without PR conflicts?

The best way to manage parallel development without conflicts is decomposing parent issues into self-contained sub-issues with correct dependency order, ensuring tasks like PII filtering are completed before dependent work like SSO is merged.

Does this issue management workflow work with the aihub-core repository?

Yes, this issue management workflow is designed for software development teams using the bbvch-ai/aihub-core repository to decompose parent issues into parallel, independently mergeable sub-issues while enforcing behavior-focused acceptance criteria.