dx-hub-dispatch

Dispatch tickets to multiple repositories via parallel Claude Code sessions.

6|3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-hub-dispatch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dx-hub-dispatch
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-hub/skills/dx-hub-dispatch
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-hub-dispatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatching a ticket to multiple repositories often requires manual coordination, opening sessions for each repo, and maintaining separate context. This Skill centralizes the workflow by reading the ticket, identifying involved repos, and launching parallel Claude Code sessions in VS Code across those repos.

Core Features & Use Cases

  • Auto-detect involved repos from the ticket content or explicit user input and spin up independent Claude sessions per repository.
  • Pre-seed each repository with the ticket context and provide cross-repo coordination notes to keep teams aligned.
  • Support ADO and Jira work items with multi-repo delegation and status tracking.

Quick Start

Run /dx-hub-dispatch with a ticket identifier to initiate multi-repo dispatch across involved repos.

Frequently Asked Questions about dx-hub-dispatch

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

FAQPage Schema
How do I dispatch a Jira work item to multiple repositories at once?

Multi-repo ticket dispatch reads the Jira work item content, auto-detects involved repos from the ticket text, and launches independent Claude Code sessions in VS Code for each target repository.

Can I use ADO work items for multi-repo delegation with Claude?

Yes, multi-repo delegation supports ADO work items by reading the ticket content, determining involved repos, and spinning up independent Claude Code sessions with pre-seeded ticket context and cross-repo coordination notes.

How do I launch parallel Claude Code sessions across different repos from a single ticket?

Parallel Claude Code sessions are launched by reading the ticket, identifying involved repos via auto-detection or explicit repo-list input, and opening independent VS Code terminals for each target repository.

Does multi-repo ticket dispatch require explicit repo-list input for every ticket?

No, explicit repo-list input is optional because the dispatch workflow supports auto-detection of involved repos directly from the ticket text, reducing manual coordination effort.

What is the best way to maintain context across parallel Claude Code sessions in different repos?

Cross-repo coordination is maintained by pre-seeding each repository with ticket context and emitting per-repo delegation prompts using a dedicated hub state directory for status tracking.

Are there limitations when auto-detecting involved repos from ticket text?

Auto-detection relies on reading the ticket content to determine involved repositories, so tickets lacking explicit repository references may require manual repo-list input to dispatch correctly.