woocommerce/woocommerce-android / .agents/skills/maestro-flow-doctor
maestro-flow-doctor
VerifiedRepair a failing WooCommerce Android Maestro flow by reproducing it against the store it runs on, inspecting Maestro selectors, patching the smallest selector/wait/setup issue, and rerunning with repeat evidence. Human-triggered only.
Maestro Flow Doctor
Use this skill only for repairing existing Maestro smoke flows under .maestro/flows/.
Ground Rules
- Run each flow against the store it declares; don't pass
--store. Flows taggedstore_sharedneed the shared store's second store and Google for WooCommerce. - Never run destructive repair loops against the shared store; the runner refuses them.
- Never ask the user to paste credentials. Validate that
.maestro/.env.localhas the required variable names without echoing values. - Use Maestro MCP as the selector source of truth:
runexecutes the YAML we ship, andinspect_screenshows the hierarchy Maestro selectors see. - Keep fixes minimal: selector, wait, setup, or fixture query changes only. Do not broaden coverage while repairing a flake.
Workflow
- Confirm the target flow path exists under
.maestro/flows/. - Run syntax and coverage checks:
.maestro/scripts/check-smoke-coverage.pysource .maestro/scripts/configure-toolchain.sh && maestro check-syntax <flow>
- Reproduce on a device:
source .maestro/scripts/configure-toolchain.sh && .maestro/scripts/run-smoke-tests.sh --seed --include-tags quarantine --device <serial> <flow>
- At the failure point, use Maestro MCP
inspect_screen. - Compare the failing selector with the hierarchy:
- Prefer
id:selectors exposed throughtestTag. - Use generated
strings.envvalues for text assertions. - Do not add
point:selectors unless the flow comment explains why no semantic selector exists.
- Prefer
- Patch the smallest file set.
- Rerun the single flow with repeat evidence:
- Non-destructive flow:
source .maestro/scripts/configure-toolchain.sh && .maestro/scripts/run-smoke-tests.sh --repeat 3 --device <serial> <flow> - Destructive flow, which uses up the fixtures of one seed, so it runs once per seed:
source .maestro/scripts/configure-toolchain.sh && for i in 1 2 3; do .maestro/scripts/run-smoke-tests.sh --seed --device <serial> <flow> || break; done
- Non-destructive flow:
- Summarize:
- root cause,
- files changed,
- repeat result,
- whether the flow remains quarantined.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |