dx-hub-status
Show hub dispatch status — which repos are running, done, blocked or failed. Use for 'hub status', 'what's running'.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 7
- Forks
- 3
01 前言 Front Matter
- name
- dx-hub-status
- description
- Show hub dispatch status — which repos are running, done, blocked or failed. Use for 'hub status', 'what's running'.
- allowed-tools
- [ "Read", "Glob", "Grep", "Write", "Bash" ]
- argument-hint
- [ticket-id (optional) | --clean]
03 SKILL.md 正文
You display the status of hub dispatches across all configured repos.
Before anything else, read .ai/config.yaml. If hub.enabled is not true, STOP with:
Hub mode is not enabled. Run `/dx-hub-init` first.
1. Parse Arguments
- No argument → show all active dispatches (summary table)
<ticket-id>→ detailed view for that one ticket--clean→ remove state entries older thanhub.state-ttl, report count
Read from config:
hub.state-ttl— retention period for clean mode (default:7d)repos[]— list of repos with paths (for reading spec dirs in detailed view)
2. Load Status Files
Glob state/*/status.json to find all dispatch state files.
If no files found, print: No active dispatches found. Run /dx-hub-dispatch to start one. and STOP.
3. Display
All dispatches (no argument)
Print a summary table:
Hub Dispatch Status
───────────────────────────────────────────────────
┌──────────┬─────────────────────────┬──────────────┬──────────┐
│ Ticket │ Title │ Repo │ Status │
├──────────┼─────────────────────────┼──────────────┼──────────┤
│ 2471234 │ Add user profile page │ repo-fe │ done │
│ │ │ repo-be │ running │
│ 2471189 │ Fix auth timeout │ repo-be │ blocked │
└──────────┴─────────────────────────┴──────────────┴──────────┘
Legend: done ✓ running ⟳ blocked ⚠ failed ✗
For multi-repo dispatches, show ticket and title only on the first row.
Single ticket (<ticket-id> argument)
Find state/<ticket-id>/status.json. If not found, print: No dispatch found for ticket <ticket-id>. and STOP.
Read the status file and print:
## Dispatch: <ticket-id> — <title>
**Type:** <type>
**Skill:** <skill>
**Started:** <started timestamp>
### Repo Status
| Repo | Status |
|------|--------|
| <repo-a> | done |
| <repo-b> | running |
If any repo is blocked, add:
⚠ <repo-name> is blocked — switch to its terminal to investigate.
If any repo is done, optionally check for spec files in that repo:
ls <repo-path>/.ai/specs/<ticket-id>-*/
Report which pipeline artifacts exist (raw-story.md, explain.md, implement.md, pr.md) as a quick progress indicator.
Cross-repo context
Print:
Context file: state/<ticket-id>/context.md
Clean mode (--clean)
- Parse
hub.state-ttl— support7d,30d,24hformats. Convert to seconds. - Check each
state/<dir>/status.json:- Read
startedtimestamp - If age exceeds TTL AND no repo is
running, delete the directory with onerm -rf state/<ticket-id>per directory, the ticket id written out literally — neverstateorstate/itself, no shell variable, loop or$(...)as the target (Claude Code v2.1.281+ stops on those for a permission prompt even in bypass mode, which stalls a pipeline run) - Never clean dispatches where any repo is still
running
- Read
- Print summary:
Hub State Cleaned
─────────────────
Removed: <N> dispatch dir(s) older than <hub.state-ttl>
Retained: <M> dispatch dir(s)
Examples
Check overall hub progress
/dx-hub-status
Shows summary table of all dispatches with per-repo status.
Inspect a specific ticket
/dx-hub-status 2471234
Shows detailed view with repo statuses. For completed repos, shows which spec files exist.
Clean up old state
/dx-hub-status --clean
Removes dispatch state directories older than hub.state-ttl (default 7 days).
Troubleshooting
"No active dispatches found"
Cause: No status.json files in state/.
Fix: Run /dx-hub-dispatch <ticket-id> to start a dispatch.
Status shows "running" but terminal is idle
Cause: The repo's Claude session finished but did not update status.json (prompt instruction was not followed).
Fix: Manually edit state/<ticket-id>/status.json to set the correct status, or check the repo's spec directory for completion indicators.
Rules
- Read config first — always check
hub.enabledbefore doing anything else - Never hardcode paths — state dir is always
state/relative to hub CWD - Respect running dispatches — never clean entries where any repo is
running - Generic examples only — no client org names, project names, or real repo names
04 同仓库更多 Skills
dx-hub-init
Initialize a hub directory for multi-repo orchestration. Discovers sibling repos, merges configs, validates CLI compatibility. Use when setting up hub mode for the first time. Trigger on "init hub", "set up hub", "multi-repo setup".
dx-hub-dispatch
Dispatch a ticket to several repos — open an independent Claude session per repo in VS Code terminals. Use for 'hub dispatch', 'work on ticket across repos'.
dx-hub-config
View and edit hub configuration — add repos, adjust terminal delay. Use to manage hub settings. Trigger on "hub config", "add repo to hub", "terminal delay".
dx-discover-repos
Resolve which repos a work item touches (explicit directive → simple block → cross-repo table → LLM). Used by the KAI-HUB router to fan an agent out across repos; 'which repos'.
dx-upgrade
Upgrade a consumer project to the installed plugin versions — run dx-doctor, fix stale and missing files, list manual actions. Use after upgrading plugins.
dx-ticket-analyze
Research an ADO/Jira ticket and list the source files and assets it involves. Use for 'analyze ticket', 'what files does this touch?', 'find files for this story'.