verify
- Repo stars 357
- License GPL-2.0
- Author updated Live
- Author repo woocommerce-ios
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @woocommerce · GPL-2.0
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: verify
description: Build the app, launch on simulator, and verify feature behavior via mobile-mcp interaction. Use…
category: engineering
runtime: no special runtime
---
# verify output preview
## PART A: Task fit
- Use case: Build the app, launch on simulator, and verify feature behavior via mobile-mcp interaction. Use after making changes to visually confirm they work from a user's perspective..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Step 1: Assess the Environment / Step 2: Detect Feature Scope / Step 3: Start Mock Server (only if needed)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Build the app, launch on simulator, and verify feature behavior via mobile-mcp interaction. Use after making changes to visually confirm they work from a user's perspective.”.
- **02** When the source has headings, the agent prioritizes “Step 1: Assess the Environment / Step 2: Detect Feature Scope / Step 3: Start Mock Server (only if needed)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source mentions slash commands such as `/mocks`, `/simulator`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Step 1: Assess the Environment / Step 2: Detect Feature Scope / Step 3: Start Mock Server (only if needed)”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: verify
description: Build the app, launch on simulator, and verify feature behavior via mobile-mcp interaction. Use…
category: engineering
source: woocommerce/woocommerce-ios
---
# verify
## When to use
- Build the app, launch on simulator, and verify feature behavior via mobile-mcp interaction. Use after making changes t…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Step 1: Assess the Environment / Step 2: Detect Feature Scope / Step 3: Start Mock Server (only if needed)” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "verify" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Step 1: Assess the Environment / Step 2: Detect Feature Scope / Step 3: Start Mock Server (only if needed)
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}E2E Simulator Verification
Build the app, launch it on the iOS simulator, and verify the affected feature areas work correctly by navigating the UI and checking for expected elements.
Read .claude/references/screen-identifiers.md to understand how to identify screens and navigate between them.
Step 1: Assess the Environment
Before setting up anything, determine what's already available:
- Simulator: is an iPhone simulator already booted? (
xcrun simctl list devices booted | grep iPhone) - App state: is the app already installed? (
xcrun simctl listapps <UDID> 2>/dev/null | grep com.automattic.woocommerce) - Session state: launch the app and check the current screen — is the user already logged in (tab bar visible) or on the login screen?
Most verification happens during development where the simulator has a current build and an active session. In this case, you only need to build your changes and re-launch — no mock server or login flow needed.
Use the mocked environment (WireMock + logout-at-launch) only when:
- There is no existing session / data on the simulator
- You need deterministic mock data (e.g., verifying specific order states)
- The user explicitly requests mocked verification
If a mocked environment is not needed, skip Steps 3 and the mock-specific launch args in Step 5.
Step 2: Detect Feature Scope
Determine which features were changed:
git diff --name-only trunk...HEADIf no diff against trunk, fall back to git diff --name-only HEAD~1.
Read .claude/references/feature-map.json and match changed file paths against pathPatterns for each feature. Collect all matched features. If no features match, skip verification entirely — report which files changed, note that none matched any feature path pattern, and stop (do not proceed to Steps 3-8).
Step 3: Start Mock Server (only if needed)
Use the /mocks skill approach: start WireMock on port 8282 in the background. Verify it's running before proceeding.
Step 4: Build the App
Use the /simulator skill approach to discover a booted simulator UDID.
xcodebuild -workspace WooCommerce.xcworkspace -scheme WooCommerce \
-destination "platform=iOS Simulator,id=<UDID>" -sdk iphonesimulator \
build 2>&1 | tail -30If the build fails, analyze errors and report. The build must succeed — verification requires the current code.
Step 5: Launch App
If using mocked environment, collect launch arguments:
logout-at-launch,disable-animations,mocked-wpcom-api,-ui_testing,-mocks-port,8282- Append any feature-specific
launchArgsfromfeature-map.json - Mock credentials (for login flow): site
http://yourwoosite.com, emailt@wp.com, passwordpw
Launch using xcrun simctl launch (supports launch arguments, unlike mobile-mcp's launch_app):
xcrun simctl launch <UDID> com.automattic.woocommerce <all-args-space-separated>If using existing environment, launch without mock args:
xcrun simctl launch <UDID> com.automattic.woocommerceWait 5 seconds for the app to settle.
Step 6: Navigate and Verify
Use mobile-mcp tools (list_elements_on_screen, click_on_screen_at_coordinates, take_screenshot) to interact with the app.
Consult .claude/references/screen-identifiers.md for screen identification, element lookup, and navigation flows (including login flow when using mocked environment).
For each matched feature from the feature map:
- Navigate to the feature's screen following the navigation flows in screen-identifiers.md
- List elements to confirm you arrived at the right screen (match primary identifier)
- Screenshot and visually assess the screen
- Verify the feature's
verifyElementsfrom feature-map.json are present - Interact if the feature defines
interactions— execute each action
Verification Criteria
- The screen loaded (not blank/empty/error)
- Expected accessibility elements are present
- No crash or unexpected error state visible
Step 7: Report Results
Summarize:
- Features verified: list each feature and pass/fail
- Screenshots taken: file paths
- Missing elements: any expected elements not found
- Visual assessment: brief description of what the UI looks like
- Issues found: crashes, error states, unexpected behavior
Step 8: Cleanup
xcrun simctl terminate <UDID> com.automattic.woocommerceIf mock server was started, stop it using the /mocks skill approach (kill by port).
Decide Fit First
Design Intent
How To Use It
Boundaries And Review