Agent Skills › getsentry/XcodeBuildMCP › xcodebuildmcp-runtime-boundary-review

xcodebuildmcp-runtime-boundary-review

GitHub

审查XcodeBuildMCP运行时边界变更，涵盖MCP、CLI、守护进程及IDE桥接路由。默认仅审查不修改代码，需检查相关源码、清单及文档，验证路由逻辑与错误处理，确保符合架构规范。

.agents/skills/xcodebuildmcp-runtime-boundary-review/SKILL.md getsentry/XcodeBuildMCP

Trigger Scenarios

审查XcodeBuildMCP运行时边界变更检查MCP、CLI或守护进程的路由逻辑

Install

npx skills add getsentry/XcodeBuildMCP --skill xcodebuildmcp-runtime-boundary-review -g -y

More Options

Non-standard path

npx skills add https://github.com/getsentry/XcodeBuildMCP/tree/main/.agents/skills/xcodebuildmcp-runtime-boundary-review -g -y

Use without installing

npx skills use getsentry/XcodeBuildMCP@xcodebuildmcp-runtime-boundary-review

指定 Agent (Claude Code)

npx skills add getsentry/XcodeBuildMCP --skill xcodebuildmcp-runtime-boundary-review -a claude-code -g -y

安装 repo 全部 skill

npx skills add getsentry/XcodeBuildMCP --all -g -y

预览 repo 内 skill

npx skills add getsentry/XcodeBuildMCP --list

SKILL.md

Frontmatter

{
    "name": "xcodebuildmcp-runtime-boundary-review",
    "description": "Use when reviewing XcodeBuildMCP runtime boundary changes across MCP, direct CLI invocation, daemon-routed tools, and Xcode IDE bridge routing."
}

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.ts
src/runtime/tool-invoker.ts
src/runtime/types.ts
src/cli/**
src/daemon/**
manifests/tools/*.yaml
manifests/workflows/*.yaml
xcodebuildmcp.com/app/docs/_content/architecture-runtime-boundaries.mdx
xcodebuildmcp.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.stateful requires 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.