Xcodebuildmcp Tool Contract Review
- 21 installs
- 6.2k repo stars
- Updated August 4, 2026
- cameroncooke/xcodebuildmcp
xcodebuildmcp-tool-contract-review is a skill that reviews XcodeBuildMCP tool contract changes across implementation, manifests, workflows, and output schema metadata.
About
This skill reviews XcodeBuildMCP tool contract changes across implementation, manifests, workflow membership, output schema metadata, and next-step templates. It enforces guardrails such as the manifest id matching the filename, tool modules exporting named schema and handler, and nextSteps.toolId referencing existing manifest tool IDs. It is review-only unless implementation changes are explicitly requested.
- Reviews XcodeBuildMCP tool contract changes across implementation, manifests, and workflow exposure
- Enforces manifest id matching filename, unique names.mcp, and outputSchema for structured-output tools
- Flags parallel legacy or duplicate implementation paths
Xcodebuildmcp Tool Contract Review by the numbers
- 21 all-time installs (skills.sh)
- Ranked #723 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
xcodebuildmcp-tool-contract-review capabilities & compatibility
- Capabilities
- code review · testing
- Use cases
- code review · testing
What xcodebuildmcp-tool-contract-review says it does
Review guardrails for tool contract changes across implementation, manifests, and workflow exposure.
Tool module exports named `schema` and `handler`.
`nextSteps.toolId` references existing manifest tool IDs.
npx skills add https://github.com/cameroncooke/xcodebuildmcp --skill xcodebuildmcp-tool-contract-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 tool contract changes across code, manifests, and workflows.
Who is it for?
Keeping XcodeBuildMCP tool implementations, manifests, and workflow exposure consistent.
Skip if: Editing product code, which it avoids unless explicitly requested.
When should I use this skill?
When reviewing XcodeBuildMCP tool contract changes across implementation, manifests, or workflow membership.
What you get
Tool contract changes are verified consistent across code, manifests, and workflows.
- Findings on tool contract, manifest, and workflow guardrails
By the numbers
- 9 tool-contract guardrail checks
Files
XcodeBuildMCP Tool Contract Review
Review guardrails for tool contract changes across implementation, manifests, and workflow exposure.
Review scope
- Review-only by default.
- Do not edit product code unless the user explicitly requests implementation changes.
Files to inspect
src/mcp/tools/**manifests/tools/*.yamlmanifests/workflows/*.yamlsrc/core/manifest/schema.tssrc/runtime/tool-catalog.tssrc/runtime/types.tsxcodebuildmcp.com/app/docs/_content/tool-authoring.mdxxcodebuildmcp.com/app/docs/_content/architecture-manifest-visibility.mdx
Guardrails
- Manifest
idmatches filename. - Manifest
modulepoints to implementation path without extension. - Tool module exports named
schemaandhandler. names.mcpremains globally unique.names.clistays workflow-local and consistent with CLI docs/fixtures.- Tool appears in at least one workflow unless intentionally hidden by availability.
outputSchemais present for tools that setctx.structuredOutput.nextSteps.toolIdreferences existing manifest tool IDs.- Avoid parallel legacy paths or duplicate implementation paths.
Validation
npm run typechecknpm test -- src/core/manifest/__tests__/schema.test.tsnpm test -- src/runtime/__tests__/tool-invoker.test.tsnpx skill-check .agents/skills/xcodebuildmcp-tool-contract-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 manifest rules are enforced?
The manifest id matches the filename, module points to the implementation path without extension, and names.mcp stays globally unique.
When is outputSchema required?
outputSchema is present for tools that set ctx.structuredOutput.