القائمة
Rebuild the iOS app after code changes and install it on the booted simulator. Use after editing Swift source files when you need a fresh build without re-running init.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 | build |
| description | Rebuild the iOS app after code changes and install it on the booted simulator. Use after editing Swift source files when you need a fresh build without re-running init. |
| argument-hint | [--scheme=<name>] [--simulator=<name>] |
Rebuild the app and install it on the simulator using Grantiva's build pipeline. Use this after making code changes - it's faster than re-running /swift-assist:init when the project is already configured.
/swift-assist:build
/swift-assist:build --scheme=MyApp
/swift-assist:build --scheme=MyApp --simulator="iPhone 16 Pro"
--scheme=<name>: Xcode scheme to build (reads from grantiva.yml if omitted)--simulator=<name>: Target simulator (reads from grantiva.yml if omitted)Load scheme and simulator from grantiva.yml if not provided via arguments:
cat grantiva.yml
If grantiva.yml doesn't exist, tell the user to run /swift-assist:init first.
Use Grantiva to build:
grantiva build
This resolves the project, boots the simulator if needed, and compiles the app. If build_settings are defined in grantiva.yml, they're applied automatically.
If the build fails, report the full error output and stop. Do not proceed.
If the Grantiva runner was active, restart it so it reconnects to the new build:
grantiva runner start --bundle-id <BUNDLE_ID> --simulator "<SIMULATOR>"
Build complete.
Scheme: <SCHEME>
Simulator: <SIMULATOR>
Bundle ID: <BUNDLE_ID>
App is running. Run /swift-assist:doctor to audit or /swift-assist:test to run flows.
grantiva.yml before asking the usergrantiva for building - never call xcodebuild directly