cmux (coder) / Mux — Prompts
Excerpt 1: .mux/skills/deep-review/SKILL.md — Sub-Agent Review Orchestration
---
name: deep-review
description: Sub-agent powered code reviews spanning correctness, tests, consistency, and fit
advertise: false
---
# Deep Review Mode
Provide an **excellent code review** by defaulting to **parallelism**.
You should use sub-agents to review the change from multiple angles (correctness, tests,
consistency, UX, performance, safety). Each sub-agent should have a focused mandate and
return actionable findings with file paths.
## Spawn the right sub-agents (change-type aware)
Spawn **2–5** sub-agents depending on scope. Tailor them to the change.
### Suggested sub-agent set
- **Correctness & edge cases** (always) — find logic bugs, missing error handling, race conditions
- **Tests & verification** (always) — evaluate coverage, propose missing tests
- **Consistency & architecture** (usually) — ensure changes match existing patterns
- **UX & accessibility** (when UI changed) — keyboard flows, a11y, empty/loading/error states
- **Performance & reliability** (when hot paths changed) — latency, blocking calls, memory growth
- **Docs & developer experience** (when public API changed) — clarity, correctness, link integrity
Prompting technique: Parallel sub-agent dispatch — explicit mandate to spawn 2-5 sub-agents with specific roles. Change-type-aware routing (UI changes get UX sub-agent, hot paths get performance sub-agent). This is the most sophisticated prompt orchestration pattern in this batch.
## Attribution Footer
Public work (issues/PRs/commits) must use 🤖 in the title and include this footer in the body:
_Generated with `mux` • Model: `<modelString>` • Thinking: `<thinkingLevel>` • Cost: `$<costs>`_
<!-- mux-attribution: model=<modelString> thinking=<thinkingLevel> costs=<costs> -->
Always check $MUX_MODEL_STRING, $MUX_THINKING_LEVEL, and $MUX_COSTS_USD via bash before
creating or updating PRs—include them in the footer if set.
## Lifecycle Rules
- Never enable auto-merge or merge into main yourself. The user must explicitly merge PRs.
- PR readiness: (1) Codex confirms approval, (2) all Codex review threads resolved,
(3) all required CI checks pass. MUST NOT report success before these conditions are met.
Prompting technique: Iron-law constraints with explicit completion criteria ("MUST NOT report success before these conditions are met") and traceability metadata injection (model + cost in every PR).
Excerpt 3: .mux/agents/plan.md — Agent Mode Extension
---
name: Plan
base: plan
---
- Attach a net LoC estimate (product code only) to each recommended approach.
Prompting technique: Minimal delta extension — extends the base plan mode with a single additional requirement (LoC estimate). Demonstrates how Mux's agent configuration format works: YAML frontmatter + markdown body.