Skip to content
Back to skills

Mobilebuildmcp Test Boundary Review

ASecurity

Use when reviewing MobileBuildMCP tests for correct unit, snapshot, schema, smoke, and external process boundaries.

  • 6,449 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 30, 2026
ai-agentstypescriptrailstesting

Works with

  • mcp

Security analysis

A100/100

Scanned September 30, 2026

npx -y skills add getsentry/XcodeBuildMCP --skill mobilebuildmcp-test-boundary-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mobilebuildmcp Test Boundary Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Mobilebuildmcp Test Boundary Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/getsentry-mobilebuildmcp-test-boundary-review/badge)](https://www.skillsdirectory.com/skills/getsentry-mobilebuildmcp-test-boundary-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: mobilebuildmcp-test-boundary-review
description: Use when reviewing MobileBuildMCP tests for correct unit, snapshot, schema, smoke, and external process boundaries.
---

# MobileBuildMCP 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/**`
- `scripts/**/__tests__/**`
- `package.json`
- `xcodebuildmcp.com/app/docs/_content/testing.mdx`
- `xcodebuildmcp.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 test`
- `npm run typecheck`
- If fixtures/schemas changed: `npm run test:snapshots` and `npm run test:schema-fixtures`
- `npx skill-check .agents/skills/mobilebuildmcp-test-boundary-review`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…