Xcodebuildmcp Test Boundary Review
- 21 installs
- 6.2k repo stars
- Updated August 4, 2026
- cameroncooke/xcodebuildmcp
xcodebuildmcp-test-boundary-review is a skill that reviews XcodeBuildMCP tests for correct unit, snapshot, schema, smoke, and external-process boundaries.
About
This skill reviews XcodeBuildMCP tests for correct unit, snapshot, schema, smoke, and external process boundaries. It enforces guardrails such as unit tests injecting command, filesystem, and external dependencies and never calling real xcodebuild, xcrun, AXe, devices, or simulators. It is review-only unless implementation changes are explicitly requested.
- Reviews XcodeBuildMCP tests for correct unit, snapshot, schema, smoke, and external-process boundaries
- Enforces that unit tests inject dependencies and never call real xcodebuild, xcrun, devices, or simulators
- Treats snapshot updates as contract changes requiring review
Xcodebuildmcp Test Boundary Review by the numbers
- 21 all-time installs (skills.sh)
- Ranked #723 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
xcodebuildmcp-test-boundary-review capabilities & compatibility
- Capabilities
- code review · testing
- Use cases
- code review · testing
What xcodebuildmcp-test-boundary-review says it does
Review guardrails for test isolation, scope, and contract validation.
Unit tests do not call real `xcodebuild`, `xcrun`, AXe, devices, or simulators.
Do not add fake e2e/snapshot state to force test success.
npx skills add https://github.com/cameroncooke/xcodebuildmcp --skill xcodebuildmcp-test-boundary-reviewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 21 |
|---|---|
| repo stars | ★ 6.2k |
| Last updated | August 4, 2026 |
| Repository | cameroncooke/xcodebuildmcp ↗ |
What it does
Review XcodeBuildMCP test changes for correct isolation and boundary usage.
Who is it for?
Keeping unit tests isolated with injected dependencies and no real xcodebuild or simulator calls.
Skip if: Editing product code, which it avoids unless explicitly requested.
When should I use this skill?
When reviewing XcodeBuildMCP tests for unit, snapshot, schema, smoke, or external process boundaries.
What you get
Test changes are verified to keep dependencies injected and boundaries respected.
- Findings on test isolation and boundary guardrails
By the numbers
- 7 test-boundary guardrail checks
Files
XcodeBuildMCP Test Boundary Review
Review guardrails for test isolation, scope, and contract validation.
Review scope
- Review-only by default.
- Do not edit product code unless the user explicitly requests implementation changes.
Files to inspect
src/**/__tests__/**src/test-utils/**src/snapshot-tests/**package.jsonxcodebuildmcp.com/app/docs/_content/testing.mdxxcodebuildmcp.com/app/docs/_content/contributing.mdx
Guardrails
- Unit tests inject command/filesystem/external dependencies.
- Unit tests do not call real
xcodebuild,xcrun, AXe, devices, or simulators. - Prefer testing logic/executor functions over handler wrappers unless testing runtime integration.
- Use existing mock executor helpers.
- Treat snapshot updates as contract changes requiring review.
- Do not add fake e2e/snapshot state to force test success.
- Avoid unsafe TypeScript suppressions.
Validation
- Run targeted Vitest command for touched tests.
npm testnpm run typecheck- If fixtures/schemas changed:
npm run test:snapshotsandnpm run test:schema-fixtures npx skill-check .agents/skills/xcodebuildmcp-test-boundary-review
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kFAQ
What must unit tests avoid?
Calling real xcodebuild, xcrun, AXe, devices, or simulators; they inject those dependencies instead.
How are snapshot updates treated?
As contract changes requiring review, not as routine test tweaks.