874 tagged code-quality, measured the same way as everything else here.
Browse within: ai-coding 182ai-coding-assistant 164ai-assistant 116ai-framework 96copilot 96docstring-checker 61agentic-development 34ai-assisted-development 34ai-coding-agents 34brownfield 34code audit 31hooks 31ai-pipeline 27autonomous-coding 27
Command
Use when the user asks to refactor code, review code quality, or fix code smells — orchestrates the full refactoring pipeline from detection through fix, with parallel worktree isolation per independent refactoring group.
Command
Use when the user asks whether a release is ready, or to gate/verify release criteria before publishing. A thin readiness-gate that runs the existing read-only verifiers (evolve release-preflight, evolve release-consistency), adds the CI-green-on-main and no-WIP-commit checks they don't cover, then delegates execution…
Command
Use after ship completes. Three sub-reflectors (instinct, gene, failure) run in parallel to extract lessons, update gene pool, and analyze any failures. Off the latency-critical path.
Command
Use when starting a new evolve-loop cycle and the cycle goal is ambiguous or only described as a one-line objective. Generates a structured specification before any code is written. Surfaces assumptions explicitly.
Command
Security-focused code review that emits a numeric composite score (0.0–1.0) suitable for the evolve-loop Builder self-review convergence loop.
Command
Use when the user runs /evo:setup (or /evo:setup), asks to configure evolve-loop, onboard, pick per-phase models, or learn how the pipeline works. Auto-detects available LLM CLIs/subscriptions, explains the pipeline concisely, then presents THREE ready-made config presets (Recommended/Economy/Max-quality) the Go…
Command
Use after audit returns Verdict PASS. Atomic git commit + tag + ledger update. Single-writer; cannot fan-out.
Command
Use when the plan-review verdict is PROCEED (or plan-review is disabled) and code has not yet been written. Writes RED tests first, defining the contract Builder must satisfy. The mandatory hop before any implementation.
Command
Use when the user invokes /evo:verify-release or asks to check whether a release has propagated, whether the marketplace is up to date, or whether installed plugins reflect the latest version. Wraps legacy/scripts/release/marketplace-poll.sh for standalone post-publish verification.
Command Claude Code
Execute pre-task preparations and context loading.
Command Claude Code
Cleanup and persist session state before ending work.
Command Claude Code
Command "setup" from airmcp-com/mcp-standards, covering setting up ruv-swarm hooks, quick start, 1. initialize with hooks, 2. test hook functionality and test pre-edit hook.
Command Claude Code
Command "agent-metrics" from airmcp-com/mcp-standards, covering agent-metrics, usage, options, examples and all agents metrics.
Command Claude Code
This tool coordinates Claude Code's actions. It does NOT write code or create content.
Command Claude Code
Command "real-time-view" from airmcp-com/mcp-standards, covering real-time-view, usage, options, examples and start real-time view.
Command Claude Code
This tool coordinates Claude Code's actions. It does NOT write code or create content.
Command Claude Code
Command "swarm-monitor" from airmcp-com/mcp-standards, covering swarm-monitor, usage, options, examples and start monitoring.
Command Claude Code
Automatically select the optimal swarm topology based on task complexity analysis.
Command Claude Code
Command "cache-manage" from airmcp-com/mcp-standards, covering cache-manage, usage, options, examples and view cache stats.
Command Claude Code
Execute tasks in parallel for maximum efficiency.
Command Claude Code
Execute independent subtasks in parallel for maximum efficiency.
Command Claude Code
Optimize swarm topology for current workload.
Command Claude Code
Complete reference for all pair programming session commands.
Command Claude Code
Complete configuration guide for pair programming sessions.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: