Coordinate parallel GitHub epic shipping via managed sub-issue task lists.
npx skills add https://github.com/semanticpixel/abc --skill ship-epic-gh
Please help me install this Agent Skill. Skill: ship-epic-gh Source: https://github.com/semanticpixel/abc/tree/main/plugins/abc/skills/ship-epic-gh Command: npx skills add https://github.com/semanticpixel/abc --skill ship-epic-gh
Coordinating a multi-repo GitHub epic manually is slow and error-prone, especially when child tasks have interdependencies and must start only after upstream items merge.
/loop 6m /abc:ship-issue-gh <owner>/<repo>#<n> per ready child so multiple children progress concurrently.blocks:#N / blocked-by:#N (and cross-repo variants), and only starts children whose upstream blocked-by:* items are merged.<!-- ship-epic:status --> snapshot to the parent issue and maintains a deterministic terminal-block view until completion or halt.Invoke /abc:ship-epic-gh with a GitHub parent issue id like /ship-epic-gh owner/repo#123 to drive that epic through merge in parallel.
High-intent search queries and answers about installing and using this skill.
You can coordinate a multi-repo GitHub epic by using a coordinator Skill that manages a parent issue task-list, spawning parallel workers for ready children while gating execution on upstream dependencies.
Dependency graph gating works by parsing `blocks:#N` and `blocked-by:#N` labels on child issues, ensuring workers only spawn for children whose upstream blocked-by items have actually merged.
Yes, you can run multiple child issues in parallel by firing independent loop workers for each ready child, allowing concurrent progress while respecting interdependencies across repositories.
The best way to track parallel GitHub epic tasks is through automated status aggregation, which appends hidden comment snapshots to the parent issue to maintain a deterministic audit trail until completion.
Yes, epic orchestration includes cycle detection when building the label-based dependency graph, preventing infinite loops or deadlocks from circular blocked-by references across child issues.
When a coordinated GitHub epic finishes or fails, the orchestration loop uses cron deletion to self-terminate and appends a final terminal block comment to the parent issue for audit purposes.
drdanmaggsLink GitHub issues with dependencies and epics using GraphQL mutations.
hirokimryCreate a GitHub release pull request after verifying all child issues are closed.
semanticpixelCoordinate shipping of interdependent Trello cards with parallelization and automatic status updates.
wubq511Convert PRDs into epics and GitHub issues with parallel agent execution.