cmux-testing — Claude Code skill: Swift testing and test wiring
Skill for choosing verification scopes, adding tests, and validating Swift test targets in the cmux project. Decides what local and CI evidence a change needs.
npx skills add manaflow-ai/cmux --skill cmux-testing -a claude-codeWhat cmux-testing does
cmux-testing provides commands to run checks at different scales: from parsing changed Swift code to the full CI static recipe. Inside the repository, scripts like verify-local.py handle syntax and test-file wiring, ui-test captures UI test frames, ui-lab.py renders views to PNG without building the app, and run-e2e.sh runs E2E scenarios with screenshots.
The skill teaches you to distinguish between local and CI checks: package, native, web, or runtime. It helps you isolate a failing behavior to one focused test, then verify the fix runs the same command. For new test files in cmuxTests/, wiring in project.pbxproj is required—the skill shows how via sync-test-wiring or lint-pbxproj-test-wiring.sh.
One hard requirement: repository commands run only from a trusted checkout; even --help loads project code. Swift tests must use Swift Testing (import Testing, @Test), UI tests stay in XCTest/XCUITest. Never assert AST shape or metadata keys as a mirror of implementation—you need a real behavioral oracle or artifact.
What it helps with
- choose the right verification scope for local testing
- validate Swift test file wiring in the project
- isolate and fix a bug with proof of the regression
- render views to images without building the app
- tell if a web test failure is real or a flake
Example prompts for the agent
- Help me decide if this change needs local tests
- Set up cmux-testing and show me how to run a focused test for this feature
- I added a new file to cmuxTests—how do I verify it's wired correctly?
How to install cmux-testing
1Skills CLI (Vercel)
npx skills add manaflow-ai/cmux --skill cmux-testing -a claude-code2Manually: put the files in place
~/.claude/skills/cmux-testing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cmux-testing/
1Skills CLI (Vercel)
npx skills add manaflow-ai/cmux --skill cmux-testing -a codex2Manually: put the files in place
.agents/skills/cmux-testing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add manaflow-ai/cmux --skill cmux-testing -a cursor2Manually: put the files in place
.cursor/skills/cmux-testing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install manaflow-ai/cmux cmux-testing2Manually: put the files in place
.github/skills/cmux-testing/SKILL.md1Skills CLI (Vercel)
npx skills add manaflow-ai/cmux --skill cmux-testing -a gemini-cli2Platform CLI
gemini skills install https://github.com/manaflow-ai/cmux --path skills/cmux-testingManually: put the files in place
.devin/skills/cmux-testing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add manaflow-ai/cmux --skill cmux-testing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set12
The whole set →Similar
Questions about cmux-testing
How do I install cmux-testing in Claude Code?
Run npx skills add manaflow-ai/cmux --skill cmux-testing -a claude-code, then find ~/.claude/skills/cmux-testing/SKILL.md.
What does cmux-testing do?
It provides commands to pick verification scopes (syntax, tests, wiring), isolate bugs, and validate Swift targets in cmux. It helps you decide what local or CI evidence a change requires.
Should I migrate XCTest to Swift Testing?
Swift Testing is used for new unit and integration targets. Migrate XCTest only if you're already editing that file. UI tests remain in XCTest/XCUITest.