Xcodebuildmcp Runtime Boundary Review
- 21 installs
- 6.2k repo stars
- Updated August 4, 2026
- cameroncooke/xcodebuildmcp
xcodebuildmcp-runtime-boundary-review is a skill that reviews XcodeBuildMCP runtime routing across MCP, CLI, daemon, and Xcode IDE bridge paths.
About
This skill reviews XcodeBuildMCP runtime boundary changes across MCP, direct CLI invocation, daemon-routed tools, and the Xcode IDE bridge. It enforces guardrails such as MCP, CLI, and daemon paths using shared handlers and stateful CLI tools routing through the daemon only when required. It is review-only unless implementation changes are explicitly requested.
- Reviews XcodeBuildMCP runtime routing across MCP, CLI, daemon, and Xcode IDE bridge paths
- Enforces shared handlers and daemon routing only when routing.stateful requires it
- Flags silent fallbacks and parallel invocation paths
Xcodebuildmcp Runtime Boundary 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-runtime-boundary-review capabilities & compatibility
- Capabilities
- code review · testing
- Use cases
- code review · testing
What xcodebuildmcp-runtime-boundary-review says it does
Review guardrails for runtime routing and invocation boundaries.
MCP, CLI, and daemon paths use shared handlers.
Avoid silent fallbacks and parallel invocation paths.
npx skills add https://github.com/cameroncooke/xcodebuildmcp --skill xcodebuildmcp-runtime-boundary-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 runtime routing and invocation boundaries for regressions.
Who is it for?
Keeping MCP, CLI, and daemon invocation paths on shared handlers with correct daemon routing.
Skip if: Editing product code, which it avoids unless explicitly requested.
When should I use this skill?
When reviewing XcodeBuildMCP runtime boundary, CLI, daemon, or Xcode IDE bridge routing changes.
What you get
Runtime routing changes are verified to share handlers and avoid parallel paths.
- Findings on runtime routing boundary guardrails
By the numbers
- 7 runtime guardrail checks
Files
XcodeBuildMCP Runtime Boundary Review
Review guardrails for runtime routing and invocation boundaries.
Review scope
- Review-only by default.
- Do not edit product code unless the user explicitly requests implementation changes.
Files to inspect
src/runtime/tool-catalog.tssrc/runtime/tool-invoker.tssrc/runtime/types.tssrc/cli/**src/daemon/**manifests/tools/*.yamlmanifests/workflows/*.yamlxcodebuildmcp.com/app/docs/_content/architecture-runtime-boundaries.mdxxcodebuildmcp.com/app/docs/_content/architecture-manifest-visibility.mdx
Guardrails
- MCP, CLI, and daemon paths use shared handlers.
- Stateful CLI tools route through daemon only when
routing.statefulrequires it. - Do not treat daemon as a third manifest availability mode.
- Dynamic Xcode IDE tools keep daemon routing semantics.
- Catalog filtering respects availability, workflow selection, and predicates.
- Runtime failures surface via runtime/rendering status and fragments.
- Avoid silent fallbacks and parallel invocation paths.
Validation
npm test -- src/runtime/__tests__/tool-invoker.test.tsnpm run typechecknpx skill-check .agents/skills/xcodebuildmcp-runtime-boundary-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
When should stateful tools use the daemon?
Stateful CLI tools route through the daemon only when routing.stateful requires it.
What is explicitly discouraged?
Silent fallbacks and parallel invocation paths.