How do I install the IOS Debugger Agent skill?

Run npx skillmds@latest add coderabbitai/ios-debugger-agent 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 IOS Debugger Agent safe to use?

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

Which AI agents work with IOS Debugger Agent?

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 IOS Debugger Agent free to use?

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

Who published IOS Debugger Agent?

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

IOS Debugger Agent by coderabbitai — Agent Skill

Name: IOS Debugger Agent
Author: coderabbitai

IOS Debugger Agent

Use XcodeBuildMCP to build, run, launch, and debug the current iOS project on a booted simulator. Trigger when asked to run an iOS app, interact with the simulator UI, inspect on-screen state, capture logs/console output, or diagnose runtime behavior using XcodeBuildMCP tools.

coderabbitai 3205bf4 2 files · 2.9 KB Updated Sep 17, 2026

File contents

iOS Debugger Agent

Overview

Use XcodeBuildMCP to build and run the current project scheme on a booted iOS simulator, interact with the UI, and capture logs. Prefer the MCP tools for simulator control, logs, and view inspection.

Core Workflow

Follow this sequence unless the user asks for a narrower action.

1) Discover the booted simulator

Call mcp__XcodeBuildMCP__list_sims and select the simulator with state Booted.
If none are booted, ask the user to boot one (do not boot automatically unless asked).

2) Set session defaults

Call mcp__XcodeBuildMCP__session-set-defaults with:
- projectPath or workspacePath (whichever the repo uses)
- scheme for the current app
- simulatorId from the booted device
- Optional: configuration: "Debug", useLatestOS: true

3) Build + run (when requested)

Call mcp__XcodeBuildMCP__build_run_sim.
If the build fails, check the error output and retry (optionally with preferXcodebuild: true) or escalate to the user before attempting any UI interaction.
After a successful build, verify the app launched by calling mcp__XcodeBuildMCP__describe_ui or mcp__XcodeBuildMCP__screenshot before proceeding to UI interaction.
If the app is already built and only launch is requested, use mcp__XcodeBuildMCP__launch_app_sim.
If bundle id is unknown:
1. mcp__XcodeBuildMCP__get_sim_app_path
2. mcp__XcodeBuildMCP__get_app_bundle_id

UI Interaction & Debugging

Use these when asked to inspect or interact with the running app.

Describe UI: mcp__XcodeBuildMCP__describe_ui before tapping or swiping.
Tap: mcp__XcodeBuildMCP__tap (prefer id or label; use coordinates only if needed).
Type: mcp__XcodeBuildMCP__type_text after focusing a field.
Gestures: mcp__XcodeBuildMCP__gesture for common scrolls and edge swipes.
Screenshot: mcp__XcodeBuildMCP__screenshot for visual confirmation.

Logs & Console Output

Start logs: mcp__XcodeBuildMCP__start_sim_log_cap with the app bundle id.
Stop logs: mcp__XcodeBuildMCP__stop_sim_log_cap and summarize important lines.
For console output, set captureConsole: true and relaunch if required.

Troubleshooting

If build fails, ask whether to retry with preferXcodebuild: true.
If the wrong app launches, confirm the scheme and bundle id.
If UI elements are not hittable, re-run describe_ui after layout changes.

---name: ios-debugger-agentdescription: Use XcodeBuildMCP to build, run, launch, and debug the current iOS project on a booted simulator. Trigger when asked to run an iOS app, interact with the simulator UI, inspect on-screen state, capture logs/console output, or diagnose runtime behavior using XcodeBuildMCP tools.---# iOS Debugger Agent## OverviewUse XcodeBuildMCP to build and run the current project scheme on a booted iOS simulator, interact with the UI, and capture logs. Prefer the MCP tools for simulator control, logs, and view inspection.## Core WorkflowFollow this sequence unless the user asks for a narrower action.### 1) Discover the booted simulator- Call `mcp__XcodeBuildMCP__list_sims` and select the simulator with state `Booted`.- If none are booted, ask the user to boot one (do not boot automatically unless asked).### 2) Set session defaults- Call `mcp__XcodeBuildMCP__session-set-defaults` with: - `projectPath` or `workspacePath` (whichever the repo uses) - `scheme` for the current app - `simulatorId` from the booted device - Optional: `configuration: "Debug"`, `useLatestOS: true`### 3) Build + run (when requested)- Call `mcp__XcodeBuildMCP__build_run_sim`.- **If the build fails**, check the error output and retry (optionally with `preferXcodebuild: true`) or escalate to the user before attempting any UI interaction.- **After a successful build**, verify the app launched by calling `mcp__XcodeBuildMCP__describe_ui` or `mcp__XcodeBuildMCP__screenshot` before proceeding to UI interaction.- If the app is already built and only launch is requested, use `mcp__XcodeBuildMCP__launch_app_sim`.- If bundle id is unknown: 1) `mcp__XcodeBuildMCP__get_sim_app_path` 2) `mcp__XcodeBuildMCP__get_app_bundle_id`## UI Interaction & DebuggingUse these when asked to inspect or interact with the running app.- **Describe UI**: `mcp__XcodeBuildMCP__describe_ui` before tapping or swiping.- **Tap**: `mcp__XcodeBuildMCP__tap` (prefer `id` or `label`; use coordinates only if needed).- **Type**: `mcp__XcodeBuildMCP__type_text` after focusing a field.- **Gestures**: `mcp__XcodeBuildMCP__gesture` for common scrolls and edge swipes.- **Screenshot**: `mcp__XcodeBuildMCP__screenshot` for visual confirmation.## Logs & Console Output- Start logs: `mcp__XcodeBuildMCP__start_sim_log_cap` with the app bundle id.- Stop logs: `mcp__XcodeBuildMCP__stop_sim_log_cap` and summarize important lines.- For console output, set `captureConsole: true` and relaunch if required.## Troubleshooting- If build fails, ask whether to retry with `preferXcodebuild: true`.- If the wrong app launches, confirm the scheme and bundle id.- If UI elements are not hittable, re-run `describe_ui` after layout changes.

Frequently asked questions