agentbrew-add-command

Multi-agent command syncing is handled by defining commands once in a canonical markdown file, which is then automatically transformed per-agent to prevent accidental overwrites of manual edits. This safe syncing workflow keeps all agents updated from a single source.

A canonical command file is a single centralized markdown definition stored at a specific config path, needed when you want to deploy a command to every supported agent without maintaining separate per-agent copies. It serves as the single source of truth for transformations.

Registering an existing file for multi-agent deployment is supported by running the command add action, which links your current markdown file into the canonical workflow so it can be synced and automatically transformed across all agents.

Overwrite prevention is enforced by the strict syncing workflow, which relies on per-command canonical files and automatic per-agent format transformations, ensuring manual edits are never accidentally overwritten during deployment across agents.

Centralizing command definitions is best achieved by creating one canonical markdown file per command, then using a sync operation to deploy it everywhere, eliminating the need to ever edit per-agent copies individually.

Editing per-agent copies directly is discouraged because the automatic syncing process deploys from the canonical file and applies per-agent format transformations, meaning direct edits will be bypassed and the agents will remain safely synchronized from the central source.