dx-hub-status

Track hub dispatch progress across repositories from state files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tracks and displays the real-time status of hub dispatches across multiple repositories, helping teams quickly understand overall progress and where action is needed.

Core Features & Use Cases

  • Consolidates per-repo statuses for a given ticket (running, done, blocked, failed) into a single view.
  • Provides both an at-a-glance summary and a detailed per-repo breakdown for triage and debugging.
  • Supports a clean, multi-repo perspective for stalled tasks and rapid triage across complex workflows.

Quick Start

Run /dx-hub-status to view all active dispatches, or /dx-hub-status <ticket-id> for a detailed view.

Frequently Asked Questions about dx-hub-status

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

FAQPage Schema
How do I track multi-repo dispatch progress across repositories?

Monitor dispatch status across multiple repos by consolidating running, done, blocked, and failed states into one view. It reads state files from state/*/status.json and config from .ai/config.yaml to provide a high-level overview and per-ticket breakdown.

What is the best way to view detailed status for a specific ticket in a multi-repo workflow?

View detailed ticket status by running /dx-hub-status <ticket-id>. This provides a per-repo breakdown for triage and debugging, showing exactly where action is needed across complex multi-repo workflows.

How do I clean up stale dispatch state files for multi-repo monitoring?

Clean up stale dispatch state files using the --clean operation with hub.state-ttl. This removes outdated status data from state/*/status.json to keep your multi-repo monitoring accurate.

Can I configure which repositories are included in the dispatch status tracking?

Yes, you can configure repository lists by editing .ai/config.yaml. The tracker honors the hub.enabled setting and repository lists defined there to filter which repos are monitored.

Why does my multi-repo dispatch status show blocked or failed repos?

A multi-repo dispatch status shows blocked or failed repos when tasks stall or encounter errors. Use the per-repo detailed view to triage and debug these stalled tasks across your workflow.