pull-requests
Pull Request Guidelines
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
- Before submitting a PR, ensure the branch name reflects the work and the base branch is correct.
More from coder/mux
deep-review
Sub-agent powered code reviews spanning correctness, tests, consistency, and fit
89react-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)
28