Skip to content
Skills Library
Programming · Testing

ce-test-xcode

/ce-test-xcode

Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.

Arguments

/ce-test-xcode [scheme name or 'current' to use default]
Original author description

Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.

How it works

  1. Run
Original SKILL.md headings · 21 lines, 263 words
SKILL.md preview
---
name: ce-test-xcode
description: "Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff."
argument-hint: "[scheme name or 'current' to use default]"
disable-model-invocation: true
---

# Xcode Simulator Test

Build and exercise an iOS app on a simulator, preserving screenshots, logs, human-verification results, and failures as evidence for the user.

**Done:**

- A completed run reports overall `PASS`, `FAIL`, or `PARTIAL` plus project, scheme, simulator, build result, per-surface `PASS` / `FAIL` / `SKIP`, console errors, human checks, and residual failures.
- Per-surface status is derived from evidence, not the user's routing choice. `PASS` requires completed passing evidence. `FAIL` records observed failing evidence until a completed retest replaces it. `SKIP` means the check has no completed outcome.
- The overall result is `FAIL` while any failure remains, `PARTIAL` when no failure remains but a scoped check is skipped, and otherwise `PASS`.
- Any failure before the app is launched with log capture running stops later stages and reports an actionable setup blocker with its evidence.

**Boundaries:** this skill tests and reports. Diagnosis and any user-approved product fix belong to `ce-debug`, invoked with its authority narrowed so it returns here without committing, pushing, or opening a PR. Keep simulator interaction within the app and flows the user placed in scope.

## Run

1. **Prepare and launch.** Read `references/setup-and-build.md`. It defines the XcodeBuildMCP availability check, project and scheme discovery, simulator choice, build, install, launch, and log-capture start.
2. **Exercise and report.** After launch, read `references/test-and-report.md`. It defines per-screen evidence, human-only flows, the SwiftUI inline-link automation limitation, what to do when a check fails, cleanup, and the fixed summary fields.

Do not replace either required read with remembered tool names. XcodeBuildMCP adapters differ by host, while their observable success conditions do not.
Files in this package (4)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB
  • references/setup-and-build.md 2 KB
  • references/test-and-report.md 4 KB

Versions

The database has no other skills named ce-test-xcode.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 97656e6a57ed (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100xcode-test
    This skill should be used when building and testing iOS apps on the simulator using XcodeBuildMCP. It handles building, installing, launching, screenshot capture, and log analysis for iOS/macOS apps.
  • 100ios-build-test
    Use when user asks to "build iOS app", "run on simulator", "test iOS", "record simulator video", "reset app", "reset onboarding", or needs Xcode builds and simulator management.
  • 90xcode-simulator-testing
    Use when asked to run /xcode-simulator-testing with a scheme name or current to build and launch an iOS app in a simulator. Not for project regeneration: use ios-build-fix.
  • 95ios-simulator-skill
    Build and test Xcode projects; launch and inspect iOS Simulator apps, navigate by accessibility labels, capture screenshots and logs, and diagnose simulator issues. Use for authorized simulator lifecycle and UI testing on macOS. Requires Xcode, Python 3.12+ and idb for…
  • 86herdr-ios-simulator
    Build, run, drive and debug iOS apps on a simulator shared with the user inside herdr. Use whenever the user wants to run, see, test or debug an iOS or iPhone app ("run it on the simulator", "show me on the iPhone", "tap through the sign-in flow", "why does it crash", "check the…
  • 90ios-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.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.