Skip to main content
affpapa.org
RU EN
skill Claude Code CX Codex Cursor GitHub Copilot

ce-test-xcode — Claude Code skill: what it does, how to install

Builds and exercises iOS apps on a simulator via XcodeBuildMCP, capturing logs and screen evidence before code handoff.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add EveryInc/compound-engineering-plugin --skill ce-test-xcode -a claude-code
Open on GitHub

What ce-test-xcode does

The skill automates iOS application checks inside a simulator. It verifies XcodeBuildMCP availability, discovers project schemes, compiles the build, installs the app, and starts log capture. Any setup failure before the app launches halts execution immediately with an actionable blocker report.

During execution, the agent walks designated surfaces, collecting screenshots, console errors, and human-verified outcomes. Status reporting relies entirely on collected evidence: PASS requires verified runs, FAIL holds until a successful retest, and PARTIAL indicates skipped scoped checks. It never touches source code directly. For diagnosis, it routes control to ce-debug with narrowed permissions that forbid commits, pushes, or pull requests.

Automation stops at SwiftUI inline links due to platform limitations, so those flows require human verification. You also must have XcodeBuildMCP configured beforehand, or the test runner halts on the first step.

What it helps with

  • exercise iOS builds inside a simulator before code handoff
  • capture console logs and screenshots as test evidence
  • route run failures to ce-debug without committing changes
  • record human-verification results for manual UI checks

Example prompts for the agent

  • Run ce-test-xcode current to verify recent changes
  • Test the iOS build using ce-test-xcode MyAppScheme
  • ce-test-xcode: check the checkout flow and capture logs

How to install ce-test-xcode

1Skills CLI (Vercel)

npx skills add EveryInc/compound-engineering-plugin --skill ce-test-xcode -a claude-code

2Manually: put the files in place

~/.claude/skills/ce-test-xcode/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ce-test-xcode/

From the same set21

The whole set →
ce-brainstorm EveryInc Turns vague ideas into a structured requirements plan through dialogue. Separates product decisions from code. Claude Code CX Codex Cursor +1 3,900installs ce-compound EveryInc A skill that captures non-obvious reasoning from solved problems as durable project knowledge. Use it when the final code works but the logic behind it might vanish when the next person reads the code. Claude Code CX Codex Cursor +1 3,700installs ce-plan EveryInc Builds structured technical implementation plans without touching production code. Useful when scoping features before passing work to execution agents. Claude Code CX Codex Cursor +1 3,700installs ce-code-review EveryInc Reviews a named diff or pull request for bugs, regressions, tests, and project standards. Use it for a current branch review or a specific PR. Claude Code CX Codex Cursor +1 3,700installs ce-work EveryInc Executes a plan document or build spec end-to-end with local verification. Ideal for implementing features without reopening architectural debates. Claude Code CX Codex Cursor +1 3,600installs ce-doc-review EveryInc This skill reviews requirements, plans, and specs through role-based reviewers. Use it to catch consequential issues in an existing document and apply fixes within the granted authority. Claude Code CX Codex Cursor +1 3,600installs ce-debug EveryInc Finds the root cause of a bug from trigger to symptom and applies a test-first fix. Useful when investigating broken behavior or failing CI logs. Claude Code CX Codex Cursor +1 3,500installs lfg EveryInc Takes a request from intake to a finished result and opens a pull request for code changes. Use it when the user explicitly wants autonomous end-to-end work. Claude Code CX Codex Cursor +1 3,500installs

Similar

cookie-debugging ChromeDevTools Skill for inspecting cookies, sessions, and authentication errors via Chrome DevTools MCP. Diagnoses 401/403, auth redirects, Set-Cookie issues, and verifies cookie consent compliance. Claude Code CX Codex Cursor +1 856installs Swarm Orchestration ruvnet Skill for managing agent swarms with parallel execution, dynamic topology, and automatic load balancing. Use when a single agent is not enough and you need to orchestrate specialists of different types. Claude Code CX Codex Cursor +1 2,100installs secops-detection-engineering official Google LLC This skill authors, validates, tests, and deploys YARA-L 2.0 rules in Google SecOps. Use it to examine detection coverage gaps. Claude Code Gemini CLI CX Codex 1,900installs nestjs-expert sickn33 Assists with Nest.js enterprise architecture, dependency injection, guards, and interceptors. Useful when designing backend modules or setting up testing pipelines. Claude Code CX Codex Cursor +1 2,700installs test-driven-development Hermes Agent (adapted from obra/superpowers) Skill that embeds TDD into your workflow: write the test first, watch it fail, then code. Forces you to see failing tests before implementation, reducing bugs and enabling safe refactoring. Claude Code CX Codex Cursor +1 477installs dfm earthtojake Reviews 3D parts for sheet metal bending, CNC machining, and injection molding. Catches design-for-manufacturing issues before sending parts to the shop. Claude Code CX Codex Cursor +1 2,000installs improve-codebase-architecture Matt Pocock This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review. Claude Code 1,163,035installs design-taste-frontend Leonxlnx This skill directs the design of public pages and work screens, then checks the result in a browser through screenshots. Use it when an interface feels generic or unfinished. Claude Code CX Codex Cursor +1 673,100installs

Questions about ce-test-xcode

How to install ce-test-xcode in Claude Code?

Run npx skills add EveryInc/compound-engineering-plugin --skill ce-test-xcode -a claude-code.

What does ce-test-xcode do?

It compiles your iOS app, deploys it to a simulator via XcodeBuildMCP, captures screenshots and logs, and produces an evidence-backed test summary.

Can ce-test-xcode fix discovered bugs automatically?

No, the skill only tests and reports. It passes failures to ce-debug under restricted permissions that prevent automated git commits or PR creation.

Source text

SKILL.md · MIT 
---
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.

© EveryInc · MIT · EveryInc/compound-engineering-plugin

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor