agentleFS
SentryKnown publishergetsentry/MobileBuildMCP/.agents/skills/mobilebuildmcp-test-boundary-review/SKILL.md

mobilebuildmcp-test-boundary-review

Skill6.5k starsChanged 39 days agoMITView on GitHub

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

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not edit product code unless the user explicitly requests implementation changes.

    line 13
  2. Distinctive:

    Prefer testing logic/executor functions over handler wrappers unless testing runtime integration.

    line 29
  3. Distinctive:

    Use existing mock executor helpers.

    line 30
  4. Distinctive:

    Treat snapshot updates as contract changes requiring review.

    line 31
  5. Distinctive:

    Do not add fake e2e/snapshot state to force test success.

    line 32
  6. Distinctive:

    Avoid unsafe TypeScript suppressions.

    line 33
  7. Distinctive:

    Run targeted Vitest command for touched tests.

    line 37
  8. Very specific:

    If fixtures/schemas changed: npm run test:snapshots and npm run test:schema-fixtures

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 2 mentionsOct 2026: 5 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the getsentry/MobileBuildMCP repository that our weekly crawl found: only 7 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about getsentry/MobileBuildMCP

The biggest 5 of 7 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 7

Talked about on GitHub (7 times).

On GitHub · 7

2 more on GitHub

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.