wicked-bus

Emit events to the wicked-bus. Use when publishing events from a plugin, logging activity to the bus, or integrating a new system with the event bridge. Covers both programmatic (Node.js) and CLI usage.

Guide for naming wicked-bus events — helps choose event_type, domain, and subdomain when emitting events. Use when creating new events, integrating a plugin with the bus, or reviewing event naming for consistency.

Query and debug the wicked-bus. Use when checking bus health, inspecting events, debugging delivery issues, tracing event flow, or investigating why a subscriber isn't receiving events. Covers status, replay, and direct SQLite queries.

Initialize wicked-bus or connect to an existing instance. Use when setting up the bus for the first time, checking if it's running, or configuring a project to use it. Auto-triggered when any wicked-bus skill detects no config.

Show wicked-bus health, statistics, and diagnostics. Event counts, subscriber lag, provider list, database size, and configuration. Use when: "bus status", "is the bus healthy", "how many events", "show bus stats", or when diagnosing delivery issues.

Subscribe to wicked-bus events. Use when consuming events from the bus, setting up event listeners, polling for new events, or integrating as a subscriber. Covers registration, polling, acknowledgment, and filter patterns.

Check for and install wicked-bus updates. Compares installed version against npm registry, updates skills across all detected CLIs. Use when: "update wicked-bus", "check for bus updates", "wicked-bus update", or periodically to stay current.