qa-ios

Boot iOS Simulators, launch apps, and collect AX trees, screenshots, and logs into QA reports.

1|1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/laststance/skills --skill qa-ios
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-ios
Source: https://github.com/laststance/skills/tree/main/skills/qa-ios
Command: npx skills add https://github.com/laststance/skills --skill qa-ios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Driving an iOS app in the Simulator and producing a structured QA report is labor-intensive and error-prone, especially when validating across multiple states and device configurations.

Core Features & Use Cases

  • Boot and manage iOS simulators for consistent test runs.
  • Collect AX trees, screenshots, and logs per phase to build a verifiable QA record.
  • Generate a comprehensive QA report to support triage, reproduction, and handoff.

Quick Start

Launch the iOS QA workflow on a target app to begin an end-to-end simulator-based QA run.

Frequently Asked Questions about qa-ios

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

FAQPage Schema
How do I automate iOS simulator QA and generate a structured report?▼

To automate iOS simulator QA, you can boot a target device, launch the app, and collect AX trees, screenshots, and logs via simctl commands. This process produces a structured QA report to support triage, reproduction, and handoff.

What is an AX tree and how is it used in iOS simulator testing?▼

An AX tree maps the accessibility elements of an iOS app interface. During simulator testing, collecting AX trees alongside screenshots and logs helps build a verifiable QA record for uncovering bugs and validating cross-state configurations.

Do I need a specific bundle ID to run an iOS simulator QA workflow?▼

Yes, you need a known bundle ID and a booted simulator to operate reliably. Appropriate access to MCP tooling is also required to automate the workflow from boot to triage across multiple states and device configurations.

Can I validate Dark Mode and Dynamic Type using an iOS simulator?▼

Yes, you can validate Dark Mode, Dynamic Type, and landscape orientation using an iOS simulator. The QA workflow supports cross-state validation by collecting screenshots and AX trees across these different device configurations.

What is the best way to collect screenshots and logs for iOS app triage?▼

The best way to collect screenshots and logs for triage is driving an end-to-end simulator QA run. By booting a target device and launching the app, you capture AX trees and logs to produce a comprehensive, structured QA report.

Why does iOS simulator QA fail to produce a verifiable record manually?▼

Manual iOS simulator QA fails to produce a verifiable record because driving an app and validating across multiple states is labor-intensive and error-prone. Automating the collection of logs and AX trees ensures a structured, reproducible report.