debug
- 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: debug
description: Debug a failing test or build error in WooCommerce iOS Debug a build failure or test failure in…
category: engineering
runtime: no special runtime
---
# debug output preview
## PART A: Task fit
- Use case: Debug a failing test or build error in WooCommerce iOS Debug a build failure or test failure in the WooCommerce iOS project. bundle exec fastlane buildfortesting 2>&1 \ | grep -E "error:|fatal|cannot find|undefined|ambiguous" | head -30 xcodebuild -workspace WooCommerce.xcworkspace -scheme WooCommerce \ runs entirely locally. Works with Claude Code, Curso….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “For Build Failures / For Test Failures” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Debug a failing test or build error in WooCommerce iOS Debug a build failure or test failure in the WooCommerce iOS project. bundle exec fastlane buildfortesting 2>&1 \ | grep -E "error:|fatal|cannot find|undefined|ambiguous" | head -30 xcodebuild -workspace WooCommerce.xcworkspace -scheme WooCommerce \ runs entirely locally. Works with Claude Code, Curso…”.
- **02** When the source has headings, the agent prioritizes “For Build Failures / For Test Failures” 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. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
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.
Validate with a small run
Start with a small task and check whether the result follows “For Build Failures / For Test Failures”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: debug
description: Debug a failing test or build error in WooCommerce iOS Debug a build failure or test failure in…
category: engineering
source: woocommerce/woocommerce-ios
---
# debug
## When to use
- Debug a failing test or build error in WooCommerce iOS Debug a build failure or test failure in the WooCommerce iOS pr…
- 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 “For Build Failures / For Test Failures” 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. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "debug" {
input -> user goal + target files + boundaries + acceptance criteria
context -> For Build Failures / For Test Failures
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
}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 generateafter 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
xcodebuilddirectly):
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.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review