xcodebuildmcp-cli
Official skill for the XcodeBuildMCP CLI. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
Works with
--- name: xcodebuildmcp-cli description: Official skill for the XcodeBuildMCP CLI. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation). license: MIT --- # XcodeBuildMCP CLI Use XcodeBuildMCP tools via the `xcodebuildmcp` executable instead of raw `xcodebuild`, `xcrun`, or `simctl`. ## Step 1: Ensure the CLI Exists Check availability: ```bash xcodebuildmcp --help ``` If missing, install with one of: ```bash brew tap getsentry/xcodebuildmcp brew install xcodebuildmcp ``` ```bash npm install -g xcodebuildmcp@latest ``` Re-check after install: ```bash xcodebuildmcp --help ``` ## Step 2: Use Help-First Discovery Discover workflows and arguments from the CLI itself: ```bash xcodebuildmcp --help xcodebuildmcp tools xcodebuildmcp <workflow> --help xcodebuildmcp <workflow> <tool> --help ``` Use this discovery path instead of memorizing static tool lists. ## Step 3: Keep Execution Minimal - Choose the smallest command sequence that satisfies the request. - Prefer direct workflow commands over manual multi-step chains unless explicitly requested. - For simulator run intent, prefer the combined `build-and-run` command. - Do not chain `build` then `build-and-run` unless explicitly requested. ## Capability Overview `xcodebuildmcp` supports: - simulator and device build/test/run - debugging and log capture - UI automation - project discovery and scaffolding - session defaults and workflow configuration ## Exit Criteria - CLI presence is verified or installation steps are provided. - Commands are discovered via `--help` / `tools`. - Session defaults are checked before first build/run/test action.
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.

