deep-review
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.
Step 0: Establish the review surface
Before reviewing, gather context:
- Identify the change scope:
git diff --name-only(or the file list the user provides). - Skim the diff for intent and risk:
git diff. - Note which layers are touched:
- UI (React/components/styles)
- Main process / backend services
- IPC boundary / shared types
- Tooling/scripts
- Docs
- Tests
More from coder/mux
react-effects
Guidelines for when to use (and avoid) useEffect in React components
63generate-readme-screenshots
>-
31dev-server-sandbox
Run multiple isolated mux dev-server instances (temp MUX_ROOT + free ports)
30mobile-dev-server-sandbox
Connects Mux mobile (Expo web/native) to an isolated dev-server sandbox with deterministic port setup, backend pairing, and Chrome MCP interaction. Use when implementing or validating mobile features against a sandboxed Mux backend.
29dev-desktop-sandbox
Run isolated mux desktop (Electron) instances (temp MUX_ROOT + free ports)
28tbench
Terminal-Bench integration for Mux agent benchmarking and failure analysis
27