debug

Name: debug
Author: woocommerce

Engineering Community

Repo stars 357
License GPL-2.0
Author repo woocommerce-ios

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Debug a failing test or build error in WooCommerce iOS Debug a build failure or test failure in the WooCommerce iOS project. bun…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “For Build Failures”, “For Test Failures”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name debug directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “For Build Failures / For Test Failures” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Debug a build failure or test failure in the WooCommerce iOS project.

For Build Failures

Run the build and capture errors:

bundle exec fastlane build_for_testing 2>&1 \
  | grep -E "error:|fatal|cannot find|undefined|ambiguous" | head -30

Identify the failing file and error type
Read the failing file and surrounding context
Common root causes in this codebase:
- Missing module: Check Modules/Package.swift target dependencies
- Type mismatch: A Networking model changed — check if Yosemite/Storage need updates
- Cannot find type: May need bundle exec rake generate after adding GeneratedCopiable/Fakeable
- Ambiguous reference: Duplicate type names across Networking vs Storage
- CoreData model errors: Check Storage/CoreData/ model versions
Propose or apply the fix

For Test Failures

Run the specific failing test (targeted tests require xcodebuild directly):

xcodebuild -workspace WooCommerce.xcworkspace -scheme WooCommerce \
  -destination 'platform=iOS Simulator,name=iPhone 16' \
  -sdk iphonesimulator test \
  -only-testing:"<target>/<class>/<method>" 2>&1 | tail -50

Read the test file and understand what it expects
Read the implementation file being tested
Check the mock class setup
Common test failure patterns:
- Assertion mismatch: Verify expected vs actual, check mock stub values
- Async timeout: Check if mock callbacks are being invoked, verify continuation setup
- Nil unwrap: Check if mock return values are configured
- Wrong mock state: Verify spy properties are set correctly
- CoreData errors: Ensure InMemoryStorage is used, not persistent storage
- Missing @MainActor: Some tests need MainActor annotation
Propose or apply the fix

If the simulator destination fails, run xcrun simctl list devices available to discover available simulators, then re-run with a matching device name.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: 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
Author / version / license: @woocommerce · GPL-2.0
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Shell exec
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview debug.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

Debug a build failure or test failure in the WooCommerce iOS project.

## For Build Failures

1. Run the build and capture errors:
```bash
bundle exec fastlane build_for_testing 2>&1 \
  | grep -E "error:|fatal|cannot find|undefined|ambiguous" | head -30
```

2. Identify the failing file and error type
3. Read the failing file and surrounding context
4. Common root causes in this codebase:
   - **Missing module**: Check Modules/Package.swift target dependencies
   - **Type mismatch**: A Networking model changed — check if Yosemite/Storage need updates
   - **Cannot find type**: May need `bundle exec rake generate` after adding GeneratedCopiable/Fakeable
   - **Ambiguous reference**: Duplicate type names across Networking vs Storage
   - **CoreData model errors**: Check Storage/CoreData/ model versions
5. Propose or apply the fix

## For Test Failures

1. Run the specific failing test (targeted tests require `xcodebuild` directly):
```bash
xcodebuild -workspace WooCommerce.xcworkspace -scheme WooCommerce \
  -destination 'platform=iOS Simulator,name=iPhone 16' \
  -sdk iphonesimulator test \
  -only-testing:"<target>/<class>/<method>" 2>&1 | tail -50
```

2. Read the test file and understand what it expects
3. Read the implementation file being tested
4. Check the mock class setup
5. Common test failure patterns:
   - **Assertion mismatch**: Verify expected vs actual, check mock stub values
   - **Async timeout**: Check if mock callbacks are being invoked, verify continuation setup
   - **Nil unwrap**: Check if mock return values are configured
   - **Wrong mock state**: Verify spy properties are set correctly
   - **CoreData errors**: Ensure InMemoryStorage is used, not persistent storage
   - **Missing @MainActor**: Some tests need MainActor annotation

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> For Build Failures → For Test Failures
terms    -> Missing module · Type mismatch · Cannot find type · Ambiguous reference · CoreData model errors · Assertion mismatch · Async timeout · Nil unwrap
files/cmd -> bundle exec rake generate · xcodebuild · xcrun simctl list devices available · Modules/Package.swift · Yosemite/Storage · GeneratedCopiable/Fakeable · Storage/CoreData
body sha256 -> d24f2f8784a5