‹ 首页

ios-debugger-agent

@dimillian · 收录于 1 周前 · 上游提交 4 个月前

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.

适合你,如果你在 Mac 上开发 iOS 应用并需要调试模拟器行为

/ 通过 npx 安装 校验哈希
npx oh-my-skill add dimillian/skills/ios-debugger-agent
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- dimillian/skills/ios-debugger-agent
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify dimillian/skills/ios-debugger-agent
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
3846GitHub stars
~526最小装载
~526含声明引用
~567文本包总量
索引托管

怎么用

商店整理自技能原文 · 版本 05ba982 · 表述以原文为准
它做什么

装上后,Claude 能构建、运行和调试 iOS 项目,在模拟器上操作界面、查看屏幕状态、抓取日志,并诊断运行时问题。

什么时候触发

当你要求运行 iOS 应用、与模拟器界面交互、检查屏幕内容、获取日志或诊断运行时行为时触发。

装好后可以这样说
Claude 会构建项目、启动模拟器并截图。
Claude 会先描述界面,然后执行点击。
Claude 会启动日志捕获并返回摘要。
技能原文 SKILL.md作者撰写 · MIT · 05ba982

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.
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。