How do I install the Xcode CLI skill?

Run npx skillmds@latest add dazuiba/xcode-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Xcode CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Xcode CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Xcode CLI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Xcode CLI?

dazuiba (@dazuiba) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Xcode CLI by dazuiba — Agent Skill

Name: Xcode CLI
Rating: 4.2 (5 reviews)
Author: dazuiba

Xcode CLI

Xcode IDE interaction skill. Uses the xcode-cli CLI to build, diagnose, test, preview, and edit Xcode projects via MCP. Use when the user asks to build an Xcode project, view build errors, run diagnostics, run tests, render SwiftUI previews, search Apple documentation, or manage project files.

dazuiba d9ada5e 3.4 KB Updated Sep 17, 2026

File contents

xcode-cli Skill

Interact with Xcode through the xcode-cli CLI backed by the Xcode MCP bridge.

Prerequisites

Xcode 26.3 or later is installed and open with the target project
xcode-cli is installed: npm install -g xcode-cli
Bridge running: xcode-cli-ctl install (background) or xcode-cli-ctl run (foreground)

Commands

All commands: xcode-cli <cmd> [args]. When run from a project directory the matching Xcode tab is auto-selected. Use --tab <tabIdentifier> to override, or run xcode-cli windows to list available tabs. Add --json for JSON output.

Command	Usage	Notes
`windows`	`windows`	List tabs/workspaces; get `tabIdentifier`
`status`	`status`	Quick project status (windows + issues)
`build`	`build`	Build project
`build-log`	`build-log --severity error`	View build errors
`run`	`run`	Build first, then run if build succeeds; returns JSON with build errors on failure
`run-without-build`	`run-without-build`	Run without building (like Ctrl+Cmd+R)
`issues`	`issues --severity error`	Navigator issues
`file-issues`	`file-issues "MyApp/Sources/MyFile.swift"`	Single-file diagnostics, no full build
`test`	`test all` / `test list [--json]` / `test some "Target::Class/method()"`	Run/list tests
`preview`	`preview "MyApp/Sources/MyView.swift" --out ./out`	SwiftUI preview (requires `#Preview` macro)
`snippet`	`snippet "MyApp/Sources/File.swift" "print(expr)" --purpose "Inspect value"`	Execute code snippet in file context; `--purpose` describes why
`doc`	`doc "SwiftUI NavigationStack" --frameworks SwiftUI`	Search Apple documentation
`read`	`read "path/to/file"`	Read file
`ls`	`ls [-r] /`	List directory
`grep`	`grep "TODO\|FIXME"`	Search files
`glob`	`glob "*/.swift"`	Find files by pattern
`write`	`write "path/to/file" "content"`	Write file
`update`	`update "path/to/file" "old" "new" [--replace-all]`	Edit file
`mv`	`mv "Old.swift" "New.swift"`	Move/rename file
`mkdir`	`mkdir "MyApp/Sources/Feature"`	Create directory
`rm`	`rm "MyApp/Sources/Unused.swift"`	Delete file

Notes

File paths are relative to the Xcode project structure, not absolute filesystem paths.
If the bridge is not responding: xcode-cli-ctl status then xcode-cli-ctl uninstall && xcode-cli-ctl install.
Use xcode-cli call <toolName> --args '{"key":"value"}' to invoke any MCP tool directly.
run builds via MCP first; if the build fails, it returns the build error JSON and exits with code 1. On success it triggers run-without-build via AppleScript and returns { buildResult, runTriggered }.
run-without-build uses AppleScript to send a keyboard shortcut to Xcode; ensure Accessibility access is granted to Terminal/iTerm in System Settings → Privacy & Security → Accessibility.
Testing: use targetName + identifier from test list --json for exact test targeting. test some only runs tests from the active scheme's active test plan — switch scheme in Xcode if a target is missing.

---name: xcode-clidescription: Xcode IDE interaction skill. Uses the xcode-cli CLI to build, diagnose, test, preview, and edit Xcode projects via MCP. Use when the user asks to build an Xcode project, view build errors, run diagnostics, run tests, render SwiftUI previews, search Apple documentation, or manage project files.---# xcode-cli SkillInteract with Xcode through the `xcode-cli` CLI backed by the Xcode MCP bridge.## Prerequisites- Xcode 26.3 or later is installed and open with the target project- `xcode-cli` is installed: `npm install -g xcode-cli`- Bridge running: `xcode-cli-ctl install` (background) or `xcode-cli-ctl run` (foreground)## CommandsAll commands: `xcode-cli <cmd> [args]`. When run from a project directory the matching Xcode tab is auto-selected. Use `--tab <tabIdentifier>` to override, or run `xcode-cli windows` to list available tabs. Add `--json` for JSON output.| Command | Usage | Notes ||---------|-------|-------|| `windows` | `windows` | List tabs/workspaces; get `tabIdentifier` || `status` | `status` | Quick project status (windows + issues) || `build` | `build` | Build project || `build-log` | `build-log --severity error` | View build errors || `run` | `run` | Build first, then run if build succeeds; returns JSON with build errors on failure || `run-without-build` | `run-without-build` | Run without building (like Ctrl+Cmd+R) || `issues` | `issues --severity error` | Navigator issues || `file-issues` | `file-issues "MyApp/Sources/MyFile.swift"` | Single-file diagnostics, no full build || `test` | `test all` / `test list [--json]` / `test some "Target::Class/method()"` | Run/list tests || `preview` | `preview "MyApp/Sources/MyView.swift" --out ./out` | SwiftUI preview (requires `#Preview` macro) || `snippet` | `snippet "MyApp/Sources/File.swift" "print(expr)" --purpose "Inspect value"` | Execute code snippet in file context; `--purpose` describes why || `doc` | `doc "SwiftUI NavigationStack" --frameworks SwiftUI` | Search Apple documentation || `read` | `read "path/to/file"` | Read file || `ls` | `ls [-r] /` | List directory || `grep` | `grep "TODO\|FIXME"` | Search files || `glob` | `glob "**/*.swift"` | Find files by pattern || `write` | `write "path/to/file" "content"` | Write file || `update` | `update "path/to/file" "old" "new" [--replace-all]` | Edit file || `mv` | `mv "Old.swift" "New.swift"` | Move/rename file || `mkdir` | `mkdir "MyApp/Sources/Feature"` | Create directory || `rm` | `rm "MyApp/Sources/Unused.swift"` | Delete file |## Notes- File paths are relative to the Xcode project structure, not absolute filesystem paths.- If the bridge is not responding: `xcode-cli-ctl status` then `xcode-cli-ctl uninstall && xcode-cli-ctl install`.- Use `xcode-cli call <toolName> --args '{"key":"value"}'` to invoke any MCP tool directly.- `run` builds via MCP first; if the build fails, it returns the build error JSON and exits with code 1. On success it triggers run-without-build via AppleScript and returns `{ buildResult, runTriggered }`.- `run-without-build` uses AppleScript to send a keyboard shortcut to Xcode; ensure Accessibility access is granted to Terminal/iTerm in System Settings → Privacy & Security → Accessibility.- Testing: use `targetName` + `identifier` from `test list --json` for exact test targeting. `test some` only runs tests from the active scheme's active test plan — switch scheme in Xcode if a target is missing.

Frequently asked questions