What problem does it solve?
Coordinating alert channels across code, config, UI, and tests to add a new notifier type is error-prone; this skill provides a structured, multi-file pattern to extend the alerts pipeline with a new channel type safely and consistently.
Core Features & Use Cases
- Enables adding a new channel type (Discord, Slack, Pushover, Matrix, SMTP, Signal, …) to the alerts pipeline by updating the shared enum, config store, notifier, DI wiring, UI, and test suites.
- Provides a repeatable integration blueprint so teams can implement a new channel without breaking existing flows, including enum, IsReady logic, and test scaffolding.
- Use case: extend alerts to a new Slack/Discord channel to notify on incidents while preserving config persistence and test coverage.
Quick Start
Implement a new notifier channel by adding an INotifier, updating the enum and config store, wiring DI, updating the Alerts UI, and adding tests.