/deploy
Read-only deploy hand-off after a swarm finishes on a ruOS desktop — report what would ship, never push
> /plugin marketplace add ruvnet/rufloHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/deploy
Context preview
What this command does when you run it.
Read-only deploy hand-off after a swarm finishes on a ruOS desktop — report what would ship, never push
Command definition
deploy.mdname: deploy description: Read-only deploy hand-off after a swarm finishes on a ruOS desktop — report what would ship, never push
$ARGUMENTS
After a remote swarm run, report the state of a repo on the desktop so the user can decide on a deploy:
`node "${CLAUDE_PLUGIN_ROOT}/scripts/cli.mjs" deploy-info --desktop "<ref>" --repo <path-relative-to-$HOME>`
It returns branch, HEAD, dirty file count and commits ahead of upstream. The hand-off is:
- a branch or PR;
- this summary, for a human to review, merge and deploy.
The swarm is read-only for deploys. It never pushes, merges, deploys or publishes, and ruOS has no deploy tool to call. Present the summary and stop.
An agent meta-harness for Claude Code and Codex. 📖 RuFlo Explained — Build an AI Team That Plans, Remembers, Tests, and Improves A 14-chapter guide: from the basic idea to a first useful task, then memory, agent teams, plugins, cost and verification.
Repo: ruvnet/claude-flow
Other commands on ruvnet-claude-flow.
COMMAND_COMPLIANCE_REP…
Reviewed all command files in `.claude/commands/analysis/` directory to ensure proper usage…
bottleneck-detect
Analyze performance bottlenecks in swarm operations and suggest optimizations.

