Xcodebuildmcp Docs Release Review
- 21 installs
- 6.2k repo stars
- Updated August 4, 2026
- cameroncooke/xcodebuildmcp
xcodebuildmcp-docs-release-review is a skill that reviews XcodeBuildMCP documentation, changelog, release notes, and release-script changes for consistency.
About
This skill reviews XcodeBuildMCP documentation, CLI command references, website manifest generation, changelog, release notes, and release script changes. It checks guardrails such as CLI examples matching the generated catalog and release notes deriving from a valid changelog section. It is review-only unless implementation changes are explicitly requested.
- Reviews XcodeBuildMCP docs, changelog, release notes, and release scripts for consistency
- Checks that CLI examples match the generated CLI catalog and that behavior changes have changelog entries
- Review-only by default with npm build and release-notes validation steps
Xcodebuildmcp Docs Release 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-docs-release-review capabilities & compatibility
- Capabilities
- code review · documentation review · release review
- Use cases
- code review · documentation
What xcodebuildmcp-docs-release-review says it does
Review guardrails for documentation, generated references, and release flow consistency.
Review-only by default.
Release notes derive from a valid changelog section.
npx skills add https://github.com/cameroncooke/xcodebuildmcp --skill xcodebuildmcp-docs-release-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 docs, changelog, and release-flow changes for consistency.
Who is it for?
Keeping XcodeBuildMCP docs, CLI examples, and release notes aligned with the actual CLI catalog.
Skip if: Editing product code, which it avoids unless explicitly requested.
When should I use this skill?
When reviewing XcodeBuildMCP documentation, changelog, release notes, or release scripts.
What you get
Docs, CLI examples, and release notes are verified consistent with the release flow.
- Consistency findings across docs, changelog, and release scripts
By the numbers
- 9 guardrail checks
- 7 file paths inspected
Files
XcodeBuildMCP Docs and Release Review
Review guardrails for documentation, generated references, and release flow consistency.
Review scope
- Review-only by default.
- Do not edit product code unless the user explicitly requests implementation changes.
Files to inspect
README.mdCHANGELOG.mdwhen presentscripts/build-website-manifest.mjsscripts/generate-github-release-notes.mjsscripts/release.shpackage.jsonxcodebuildmcp.com/app/docs/_content/**
Guardrails
- CLI examples match generated CLI catalog/commands.
- Docs do not reference unavailable tools or workflows.
- User-facing behavior changes include changelog updates.
- Release notes derive from a valid changelog section.
- README install snippets align with release script tag replacement.
- Website manifest generation preserves expected normalized fields.
- Docs explain runtime/contracts without deprecated patterns.
- Keep docs-only work from introducing product behavior changes.
- CLI command references in changelog entries are reviewed by
xcodebuildmcp-docs-command-review.
Validation
npm run build- Release notes check when touched:
node scripts/generate-github-release-notes.mjs --version <version> --changelog CHANGELOG.mdnpx skill-check .agents/skills/xcodebuildmcp-docs-release-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 files does it inspect?
README.md, CHANGELOG.md, the website-manifest and release-notes scripts, release.sh, package.json, and docs content.
Does it edit code?
No, it is review-only by default and does not edit product code unless the user explicitly requests it.