create-report-type

Adding a new report type across microservices requires coordinating migrations, client and consumer logic in the source-service, notification labels, and frontend triggers. This Skill automates that end-to-end wiring across four distinct services to ensure consistency.

Automating PDF report generation in a RabbitMQ backend requires a migration for the report type, a source-service client and consumer to handle the message queue, and a handler to generate the PDF output.

Configuring ETCD for a reporting service workflow involves setting required keys and input parameters to wire the services together. This Skill enforces those required ETCD configuration steps and documents the process.

Yes, you can wire a notification-service label for new reports. The end-to-end creation process explicitly includes adding the label routine in the notification-service to improve usability alongside the frontend trigger.

The report migration approach requires preparing database schemas to accept the new report type. This Skill covers the migration step in the report-service as the foundational layer before implementing the client and consumer logic.