Skip to content

hashgraph-online/awesome-codex-plugins / plugins/avivsinai/agent-message-queue/skills/amq-cli

amq-cli

Verified

Coordinate coding agents through AMQ. Use for agent messages, inboxes, receipts, sessions, wake delivery, cross-project routing, managed launches, or AMQ diagnostics. Use amq-spec for collaborative design; do not use this for general message queues or single-agent work.

references/review-loop.md

View on GitHub
# Delegated review loops

Use a separate worker for a multi-round review when the host provides one and
the user or repository permits delegation. Otherwise keep the review in the
current session. AMQ does not create background workers or grant edit authority.

## Ownership

Give the worker the file or worktree paths, review scope, reviewer handle,
thread, permitted actions, and stopping condition. Use a distinct assigned
AMQ handle and resolve its full context before it sends or receives. Do not
let a worker and the main agent compete to drain the same mailbox.

A review-only worker reports findings; it does not apply fixes. An authorized
implementation worker may fix findings within its assigned files. Review
approval does not grant permission to commit, push, merge, or expand scope.

## Message flow

1. Send a `review_request` with paths and the user-visible change.
2. Keep the existing thread. The reviewer returns `review_response`.
3. Apply authorized findings, then request review of the changed files.
4. Stop when review is complete, the assigned limit is reached, or a decision
   requires the owner. Return the result, unresolved findings, and checks that
   were not performed.

Report progress as in the [co-op progress protocol](coop-mode.md#progress-protocol).

## Receive without a second consumer

With a live injecting wake, yield after independent work and drain on its
doorbell. Do not add `watch`, `monitor`, or a background polling loop to that
mailbox. Without a wake, a bounded wait may be used within the assigned task.

Select worker tools from the host's actual interface. Tool names and
background-task support are host features, not part of the AMQ protocol.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 321kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 197kUpdated Claude CodeCodexVerifiedInstall