Xcodebuildmcp Rendering Streaming Review
- 21 installs
- 6.2k repo stars
- Updated August 4, 2026
- cameroncooke/xcodebuildmcp
xcodebuildmcp-rendering-streaming-review is a skill that reviews XcodeBuildMCP rendering, streaming-fragment, and CLI output-mode changes for boundary violations.
About
This skill reviews XcodeBuildMCP rendering, streaming-fragment, next-step, and CLI output-mode changes for boundary violations. It enforces guardrails such as tool handlers not branching on CLI versus MCP output mode and streaming tools emitting typed fragments plus one final structured result. It is review-only unless implementation changes are explicitly requested.
- Reviews XcodeBuildMCP rendering, streaming-fragment, and CLI output-mode changes
- Enforces that tool handlers do not branch on CLI vs MCP output mode
- Checks that fragments carry progress while the final structured output stays canonical
Xcodebuildmcp Rendering Streaming 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-rendering-streaming-review capabilities & compatibility
- Capabilities
- code review · testing
- Use cases
- code review · testing
What xcodebuildmcp-rendering-streaming-review says it does
Review guardrails for rendering boundaries, streaming fragments, and output modes.
Tool handlers do not branch on CLI vs MCP output mode.
Streaming tools emit typed fragments and one final structured result.
npx skills add https://github.com/cameroncooke/xcodebuildmcp --skill xcodebuildmcp-rendering-streaming-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 rendering and streaming changes for output-boundary violations.
Who is it for?
Keeping rendering and streaming boundaries clean so fragments carry progress and the final structured output stays canonical.
Skip if: Editing product code, which it avoids unless explicitly requested.
When should I use this skill?
When reviewing XcodeBuildMCP rendering, streaming fragment, next-step, or CLI output mode changes.
What you get
Rendering and streaming changes are verified to respect output-mode boundaries.
- Findings on rendering and streaming boundary guardrails
By the numbers
- 8 rendering guardrail checks
Files
XcodeBuildMCP Rendering and Streaming Review
Review guardrails for rendering boundaries, streaming fragments, and output modes.
Review scope
- Review-only by default.
- Do not edit product code unless the user explicitly requests implementation changes.
Files to inspect
src/rendering/**src/types/domain-fragments.tssrc/types/runtime-status.tssrc/runtime/tool-invoker.tssrc/runtime/__tests__/tool-invoker.test.tsxcodebuildmcp.com/app/docs/_content/architecture-rendering-output.mdxxcodebuildmcp.com/app/docs/_content/architecture-tool-lifecycle.mdxxcodebuildmcp.com/app/docs/_content/output-formats.mdx
Guardrails
- Tool handlers do not branch on CLI vs MCP output mode.
- Fragments represent progress, not final contract data.
- Final structured output remains canonical.
- Do not invent
json/jsonlrender strategies. - Streaming tools emit typed fragments and one final structured result.
- Non-streaming tools do not emit unnecessary fragments.
- Keep
ctx.emitand xcodebuild pipelineemitFragmentcontexts separate. - Keep next-step rendering in runtime/rendering boundary.
Validation
npm test -- src/runtime/__tests__/tool-invoker.test.tsnpm run test:snapshotsnpm run typechecknpx skill-check .agents/skills/xcodebuildmcp-rendering-streaming-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 is the core boundary rule?
Tool handlers do not branch on CLI vs MCP output mode and the final structured output remains canonical.
What should streaming tools emit?
Typed fragments representing progress plus one final structured result.