
xcodebuildmcp-test-boundary-review
✓ Official★ 6,033by getsentry · part of getsentry/xcodebuildmcp
Use when reviewing XcodeBuildMCP tests for correct unit, snapshot, schema, smoke, and external process boundaries.
🧰 Not standalone. This skill ships with getsentry/xcodebuildmcp and only works together with that tool — install the tool first, then add this skill.
This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.
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
Copy & paste — that's it
npx skills add https://github.com/getsentry/xcodebuildmcp --skill xcodebuildmcp-test-boundary-reviewRun this in your project — your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.
Licensed under MIT— you can use, modify, and redistribute it under that license's terms.
View the full license file on GitHub →