Design RabbitMQ retry and DLQ topology using Definitions and x-death semantics.
npx skills add https://github.com/pure-golang/level85 --skill x-queue-rabbitmq
Please help me install this Agent Skill. Skill: x-queue-rabbitmq Source: https://github.com/pure-golang/level85/tree/main/.agents/skills/x-queue-rabbitmq Command: npx skills add https://github.com/pure-golang/level85 --skill x-queue-rabbitmq
It prevents brittle queue retry and DLQ behavior by giving a consistent RabbitMQ topology pattern that makes publisher/subscriber failures recoverable and predictable.
Apply this skill when designing a RabbitMQ publisher/subscriber pair and specify retry and DLQ behavior through Definitions, then implement the subscriber using NewSubscriber2 with MaxRetries and the retry queue wired back to the main exchange/queue.
High-intent search queries and answers about installing and using this skill.
A RabbitMQ retry and DLQ topology prevents infinite loops by using x-death semantics to track retry counts, routing messages to retry queues until MaxRetries is reached, then forwarding to the DLQ. Stable Definitions for exchanges, queues, and bindings make this behavior predictable and deployment-safe.
RabbitMQ publisher confirms in Go are configured using NewPublisher2 to ensure messages are reliably delivered. This Skill designs the publisher/subscriber retry behavior by combining confirms with stable topology Definitions, making publisher failures recoverable without losing messages.
RabbitMQ retry via x-death headers is triggered only when an error is present during subscriber processing and the x-death state indicates retries are below MaxRetries. The subscriber uses Nack with correct requeue behavior to route the message to the retry queue instead of looping it back to the main queue.
Consuming messages from multiple RabbitMQ queues without parallelism across queues in Go is supported using the MultiQueueSubscriber pattern. This Skill integrates MultiQueueSubscriber with NewSubscriber2 and routing-key based messaging to enable fan-in consumption while maintaining consistent retry and DLQ semantics.
RabbitMQ messages get lost or reprocessed immediately when the retry topology is brittle or Nack requeue behavior is incorrect. This Skill solves the problem by defining retry and DLQ queues via stable Definitions, ensuring the subscriber triggers retries based on x-death state and error presence until MaxRetries is reached.
ryan-nguyen-01Configure RabbitMQ topic exchanges, dead-letter queues, and retry workflows with exponential backoff.
YuriGarciaRibeiroStandardize RabbitMQ consumers with retry, DLQ routing, and channel-status updates.
HZeroxiumConfigure RabbitMQ queues with acknowledgements, retries, and dead-lettering for Java applications.
ririntoConfigures Spring AMQP messaging with RabbitTemplate, @RabbitListener, retries, and DLQ handling.
