
xcodebuildmcp-docs-release-review
✓ Official★ 6,033by getsentry · part of getsentry/xcodebuildmcp
Use when reviewing XcodeBuildMCP documentation, CLI command references, website manifest generation, changelog, release notes, and release script changes.
🧰 Not standalone. This skill ships with getsentry/xcodebuildmcp and only works together with that tool — install the tool first, then add this skill.
This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.
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.md
npx skill-check .agents/skills/xcodebuildmcp-docs-release-review
Copy & paste — that's it
npx skills add https://github.com/getsentry/xcodebuildmcp --skill xcodebuildmcp-docs-release-reviewRun this in your project — your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.
Licensed under MIT— you can use, modify, and redistribute it under that license's terms.
View the full license file on GitHub →