ios-validation

Build, install, and exercise iOS and macOS apps on simulators while capturing evidence.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/krzemienski/validationforge --skill ios-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-validation
Source: https://github.com/krzemienski/validationforge/tree/main/skill-audit-workspace/ios-validation/skill-snapshot
Command: npx skills add https://github.com/krzemienski/validationforge --skill ios-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate and document iOS and macOS app behavior on real simulator runtimes so failures, crashes, and UI regressions are detected with verifiable evidence rather than mocked assumptions.

Core Features & Use Cases

  • End-to-end build and install: run xcodebuild, locate the .app bundle, and install to a booted simulator.
  • Runtime evidence capture: capture screenshots, record video, and collect filtered system and app logs for forensic review.
  • Interaction and automation: exercise UI flows, deep links, and accessibility trees via idb or Xcode MCP tools to reproduce and demonstrate issues.
  • Crash detection and verdicts: search DiagnosticReports for recent crash artifacts and produce pass/fail criteria with cited evidence.
  • Use Case: pre-release validation to confirm a feature renders correctly, deep links navigate properly, and no crash logs or error-level entries are present before shipping.

Quick Start

Use the ios-validation skill to build the app, install it on a simulator, exercise the target flow while capturing screenshots, video, and logs into e2e-evidence for review.

Frequently Asked Questions about ios-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate an iOS app build and capture evidence on a simulator?

To validate an iOS app build on a simulator, you need to run xcodebuild, install the .app bundle to a booted simulator, and capture screenshots, video, and filtered logs into an evidence directory for review.

How does crash detection work during iOS simulator testing?

Crash detection during iOS simulator testing works by searching DiagnosticReports for recent crash artifacts after exercising your app, producing pass or fail verdicts with cited evidence for forensic review.

Can I test deep links and inspect accessibility trees in an Xcode simulator workflow?

Yes, you can test deep links and inspect accessibility trees in an Xcode simulator workflow by exercising UI flows via idb or Xcode MCP tools to reproduce and demonstrate navigation or accessibility issues.

Do I need idb or Xcode MCP tools to run end-to-end macOS and iOS UI checks?

You do not need idb or Xcode MCP tools strictly required, but they are optionally used for interaction and automation to exercise UI flows, deep links, and accessibility trees during end-to-end iOS and macOS UI checks.

What is the best way to document UI regressions for pre-release iOS validation?

The best way to document UI regressions for pre-release iOS validation is to capture runtime evidence including screenshots, video, and filtered system logs into a dedicated directory, confirming features render correctly before shipping.

Why are my mocked iOS tests not catching crashes and UI regressions?

Mocked iOS tests miss crashes and UI regressions because they lack real simulator runtime execution, whereas validating and documenting behavior on actual simulator runtimes detects failures with verifiable evidence.