Xcodebuildmcp Structured Output Review
- 21 installs
- 6.2k repo stars
- Updated August 4, 2026
- cameroncooke/xcodebuildmcp
xcodebuildmcp-structured-output-review is a skill that reviews XcodeBuildMCP structured output schema, versioning, manifest metadata, and JSON fixture compatibility.
About
This skill reviews XcodeBuildMCP structured output schema changes, schema versioning, manifest outputSchema metadata, and JSON fixture compatibility. It enforces guardrails such as the schema using the xcodebuildmcp.output.<name> format and breaking changes creating a new versioned schema file. It is review-only unless implementation changes are explicitly requested.
- Reviews XcodeBuildMCP structured-output schema and versioning changes
- Enforces schema naming, integer-string schemaVersion, and new files for breaking changes
- Checks manifest outputSchema matches the emitted structuredOutput payload
Xcodebuildmcp Structured Output Review by the numbers
- 21 all-time installs (skills.sh)
- Ranked #721 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
xcodebuildmcp-structured-output-review capabilities & compatibility
- Capabilities
- code review · testing
- Use cases
- code review · testing
What xcodebuildmcp-structured-output-review says it does
Review guardrails for structured output schema correctness and compatibility.
Breaking schema changes create a new versioned schema file.
Manifest `outputSchema` matches emitted `ctx.structuredOutput` payload.
npx skills add https://github.com/cameroncooke/xcodebuildmcp --skill xcodebuildmcp-structured-output-reviewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 21 |
|---|---|
| repo stars | ★ 6.2k |
| Last updated | August 4, 2026 |
| Repository | cameroncooke/xcodebuildmcp ↗ |
What it does
Review XcodeBuildMCP structured-output schema and versioning changes for compatibility.
Who is it for?
Ensuring structured-output schema changes are named, versioned, and backward-compatible.
Skip if: Editing product code, which it avoids unless explicitly requested.
When should I use this skill?
When reviewing XcodeBuildMCP structured output schema, schema versioning, or manifest outputSchema changes.
What you get
Schema changes are verified to follow naming, versioning, and compatibility rules.
- Findings on structured-output schema and versioning guardrails
By the numbers
- 7 structured-output guardrail checks
Files
XcodeBuildMCP Structured Output Review
Review guardrails for structured output schema correctness and compatibility.
Review scope
- Review-only by default.
- Do not edit product code unless the user explicitly requests implementation changes.
Files to inspect
schemas/structured-output/**src/core/structured-output-schema.tssrc/core/__tests__/structured-output-schema.test.tssrc/snapshot-tests/__fixtures__/json/**src/snapshot-tests/__tests__/json-fixture-schema.test.tsxcodebuildmcp.com/app/docs/_content/schema-versioning.mdxxcodebuildmcp.com/app/docs/_content/output-formats.mdx
Guardrails
schemausesxcodebuildmcp.output.<name>format.schemaVersionuses integer strings only.- Breaking schema changes create a new versioned schema file.
- Published schema versions are not removed or mutated incompatibly.
- Manifest
outputSchemamatches emittedctx.structuredOutputpayload. - JSON fixtures validate against current schema contracts.
$refusage remains compatible with bundling instructured-output-schema.ts.
Validation
npm run test:schema-fixturesnpm test -- src/core/__tests__/structured-output-schema.test.tsnpm run typechecknpx skill-check .agents/skills/xcodebuildmcp-structured-output-review
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kFAQ
What schema naming is required?
schema uses the xcodebuildmcp.output.<name> format and schemaVersion uses integer strings only.
How are breaking changes handled?
Breaking schema changes create a new versioned schema file and published versions are not mutated incompatibly.