Build and exercise an iOS app in a simulator using XcodeBuildMCP. Collect screenshots, logs, and human verification results, then report which checks passed, failed, or were skipped, alongside the overall outcome and remaining failures.
Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.
Review the instructions the agent will receive before you install.
Build and exercise an iOS app on a simulator, preserving screenshots, logs, human-verification results, and failures as evidence for the user.
Done:
PASS, FAIL, or PARTIAL plus project, scheme, simulator, build result, per-surface PASS / FAIL / SKIP, console errors, human checks, and residual failures.PASS requires completed passing evidence. FAIL records observed failing evidence until a completed retest replaces it. SKIP means the check has no completed outcome.FAIL while any failure remains, PARTIAL when no failure remains but a scoped check is skipped, and otherwise PASS.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.
references/setup-and-build.md. It defines the XcodeBuildMCP availability check, project and scheme discovery, simulator choice, build, install, launch, and log-capture start.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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Monitor an open GitHub pull request over time, respond to review feedback, and address automated check failures. Apply and push fixes, then report whether it appears ready to merge or what still blocks progress.
Develop independent solutions to a defined problem, compare them against shared requirements, and combine useful contributions into a coherent recommendation. An independent assessment and evidence checks support the selection, while unresolved tradeoffs and verification needs remain explicit.
Turn a vague feature idea into clear requirements through dialogue. Define what to build, its scope, and success criteria, then capture the result in a short chat summary or a requirements document ready for implementation planning.
Review code changes or a pull request for bugs, effects on existing behavior, test gaps, and project standards. Receive findings supported by the code and a clear account of review coverage, with local fixes available when explicitly requested.
Save working changes as local Git commits with messages that explain the outcome. Follow the project's commit style, select files explicitly, and split clearly separate changes into a few logical commits when appropriate.
Commit and push code changes, then open a pull request with a clear title and description. You can also draft or update PR descriptions and hand published requests to the follow-up monitoring workflow.