
Xcodebuildmcp Runtime Boundary Review
- 17 installs
- 6.2k repo stars
- Updated August 4, 2026
- getsentry/xcodebuildmcp
xcodebuildmcp-runtime-boundary-review audits runtime routing across MCP and CLI.
About
The xcodebuildmcp-runtime-boundary-review skill reviews runtime boundary changes across MCP, direct CLI invocation, daemon-routed tools, and Xcode IDE bridge routing for XcodeBuildMCP. Review-only by default without product code edits unless requested. Guardrails forbid treating daemon as a third manifest availability mode, keep routing tables explicit between MCP and CLI entrypoints, and ensure IDE bridge calls do not bypass documented tool contracts. Scope maps invocation paths, daemon membership, and bridge adapters. Validation recommends targeted smoke tests per touched route. Output lists boundary violations, routing ambiguities, and manifest availability mismatches. Review guardrails for runtime routing and invocation boundaries. Do not edit product code unless the user explicitly requests implementation changes. MCP, CLI, and daemon paths use shared handlers. Do not treat daemon as a third manifest availability mode. Dynamic Xcode IDE tools keep daemon routing semantics.
- Reviews MCP, CLI, daemon, and IDE bridge routing boundaries.
- Forbids daemon as third manifest availability mode.
- Keeps invocation path routing explicit and documented.
- Review-only unless implementation fixes requested.
- Recommends smoke tests per touched runtime route.
Xcodebuildmcp Runtime Boundary Review by the numbers
- 17 all-time installs (skills.sh)
- Ranked #760 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
- runtime boundary review scope · daemon availability mode guardrail
- Use cases
- code review · api development
- Platforms
- macOS
What xcodebuildmcp-runtime-boundary-review says it does
Do not treat daemon as a third manifest availability mode
Do not edit product code unless the user explicitly requests implementation changes
npx skills add https://github.com/getsentry/xcodebuildmcp --skill xcodebuildmcp-runtime-boundary-reviewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 17 |
|---|---|
| repo stars | ★ 6.2k |
| Last updated | August 4, 2026 |
| Repository | getsentry/xcodebuildmcp ↗ |
Does this change blur MCP, CLI, and daemon boundaries?
Review XcodeBuildMCP runtime boundaries across MCP, CLI, daemon, and Xcode bridge.
Who is it for?
Maintainers changing XcodeBuildMCP runtime routing or daemon tools.
Skip if: Skip for docs-only changes without runtime impact.
When should I use this skill?
User reviews runtime boundary, daemon routing, or IDE bridge changes.
What you get
Findings on routing tables, daemon membership, and bridge contracts.
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
FAQ
What does xcodebuildmcp-runtime-boundary-review do?
xcodebuildmcp-runtime-boundary-review audits runtime routing across MCP and CLI.
When should I use xcodebuildmcp-runtime-boundary-review?
User reviews runtime boundary, daemon routing, or IDE bridge changes.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.