verify

Engineering Community

Skill notes

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?

Step 2: Detect Feature Scope

Determine which features were changed: If 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. If 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 launchArgs from feature-map.json Mock credentials (for login flow): site http://yourwoosite.com, email t@wp.com, password pw Launch using xcrun simctl launch (supports launch arguments, unlike mobile-mcp's launch_app):

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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 explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview verify.preview
# Step 7: Report Results

- **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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.