agentleFS
cameroncookecameroncooke/XcodeBuildMCP/.agents/skills/mobilebuildmcp-snapshot-fixture-review/SKILL.md

mobilebuildmcp-snapshot-fixture-review

Skill6.5k starsChanged 54 days agoMITView on GitHub

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

2 other projects use a version of this.

Trending

Quiet since May.about the whole repository

Dec 2025: 1 mentionJan 2026: 4 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the cameroncooke/XcodeBuildMCP repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about cameroncooke/XcodeBuildMCP

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

See all 21

Talked about on GitHub and Bluesky (21 times).

On GitHub · 17

12 more on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Do not update fixtures only to make tests pass.

    line 28
  3. Very specific:

    Verify project-defined normalization sentinels in normalization code and tests before reporting them as implausible fixture values.

    line 33
  4. Distinctive:

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

    line 37
  5. Distinctive:

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

    line 38
  6. Distinctive:

    Do not run snapshot or smoke suites as part of an automated PR review.

    line 43
  7. Distinctive:

    Prefer one high-confidence cross-fixture finding over multiple speculative discrepancies.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 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.

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.