Menu
Run generated test flows against the app in the simulator using Grantiva. Use after /swift-assist:make-tests to execute and validate your user flows.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Apply accessibility identifier fixes from a doctor report to Swift source files. Adds .accessibilityIdentifier() modifiers to interactive elements. Use after /swift-assist:doctor.
Report test coverage across the app - how many screens have flows, how many elements have accessibility identifiers, and what to tackle next. Use for a quick health check on your testing setup.
Walk the running app using computer use, inspect the view hierarchy with Grantiva, and report elements missing accessibility identifiers. Use for accessibility audits or test preparation.
Walk the app using computer use and generate Grantiva screen definitions and flow YAML files for every discovered user flow. Use after /swift-assist:doctor for reliable tests.
Run a single named flow by name. Faster than /swift-assist:test when you're debugging one broken screen and don't want to wait for the full suite.
Generate a GitHub Actions workflow that runs Grantiva VRT in CI on every pull request. Use to add cloud visual regression testing with GitHub Check integration to your project.
| name | test |
| description | Run generated test flows against the app in the simulator using Grantiva. Use after /swift-assist:make-tests to execute and validate your user flows. |
| argument-hint | [--flow=<name>] [--all] |
Run the generated flow YAML files against the app in the simulator using grantiva run.
/swift-assist:test
/swift-assist:test --flow=login
/swift-assist:test --all
--flow=<name>: Run a specific flow (matches filename in flows/ directory)--all: Run all flows sequentially/swift-assist:make-tests first)If no flows exist:
No flow files found in flows/. Run /swift-assist:make-tests first.
List available flow files:
ls flows/*.yaml 2>/dev/null
If --flow specified, find matching file
If --all specified, collect all non-underscore-prefixed flows (skip _setup-*.yaml helper flows)
If neither specified, show available flows and ask which to run
For each flow, execute it using grantiva run:
grantiva run flows/<flow-name>.yaml
After all flows complete:
Test Execution Report
=====================
Flows run: 5 | Passed: 4 | Failed: 1
onboarding.yaml PASS
login.yaml PASS
settings.yaml FAIL
profile.yaml PASS
checkout.yaml PASS
Report any error output from failed flows so the user can diagnose and fix.