getsentry/xcodebuildmcp

xcodebuildmcp-snapshot-fixture-review

Use when reviewing XcodeBuildMCP snapshot fixture changes for MCP, CLI, and JSON output contract integrity.

First seen Apr 28, 2026

Installation

$ npx skills add getsentry/xcodebuildmcp --skill xcodebuildmcp-snapshot-fixture-review

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from getsentry/xcodebuildmcp · top by installs.

npx skills add getsentry/xcodebuildmcp

Browse all from getsentry/xcodebuildmcp

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 6.3K
License LICENSE
Default branch main
Open issues 15
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,882 B
  • docs SUMMARY.md 152 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 46 installs

SKILL.md

XcodeBuildMCP Snapshot Fixture Review

Review guardrails for fixture and snapshot contract integrity.

Review scope

  • Review-only by default.
  • Do not edit product code unless the user explicitly requests implementation changes.

Files to inspect

  • src/snapshot-tests/fixtures/**
  • src/snapshot-tests/contracts.ts
  • src/snapshot-tests/fixture-io.ts
  • src/snapshot-tests/tests/fixture-io.test.ts
  • src/snapshot-tests/tests/json-normalize.test.ts
  • src/snapshot-tests/tests/json-fixture-schema.test.ts
  • xcodebuildmcp.com/app/docs/_content/testing.mdx

Guardrails

  • Fixture updates map to intentional behavior changes.
  • Do not update fixtures only to make tests pass.
  • MCP, CLI, and JSON fixture updates stay aligned.
  • JSON fixtures preserve stable structured output envelopes.
  • Volatile values are normalized in code, not patched ad hoc in fixtures.
  • Missing fixtures are generated through the snapshot update flow.
  • Verify project-defined normalization sentinels in normalization code and tests before reporting

them as implausible fixture values. In particular, 99999 is an intentional sentinel for volatile UI capture counts.

  • Group every occurrence of the same root cause into one finding and list the affected fixtures.

Do not emit separate findings for equivalent CLI, MCP, text, or JSON drift.

  • Do not repeat a finding that is already resolved by the current diff.

Review limits

  • Review the changed fixtures and the directly relevant normalization or contract code only.
  • Do not run snapshot or smoke suites as part of an automated PR review.
  • Prefer one high-confidence cross-fixture finding over multiple speculative discrepancies.