maestro-qa

Runs Maestro mobile QA flows, fixes verified failures, and reruns targeted tests.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill maestro-qa-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maestro-qa
Source: https://github.com/gmackie/agent-skills/tree/main/skills/maestro-qa
Command: npx skills add https://github.com/gmackie/agent-skills --skill maestro-qa-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, jq, and includes scripts (resource) components.

What problem does it solve? Mobile QA on React Native and Expo apps often devolves into speculative fixes and full-suite reruns that waste time and obscure causality. This Skill enforces a disciplined loop: prove the failure with a report-only Maestro pass, fix one verified issue at a time, and rerun only the narrowest failing flow before broadening back out. ## Core Features & Use Cases - Report-Only Baseline: Starts every session with a non-mutating Maestro run that captures artifacts and HTML or JUnit reports as evidence. - Strict Fix Loop: Isolates a single verified failure, classifies its owner (app bug, stale flow, environment, or backend), applies the smallest fix, and reruns the narrowest surface first. - Consistent Helper Script: The bundled run-maestro-qa.sh wrapper keeps artifact paths, report formats, tag filtering, and dry-run previews consistent across runs. - Use Case: When asked to fix a broken onboarding flow, the Skill runs the report pass, isolates the failing step, applies a minimal selector or code fix, reruns the onboarding flow plus nearby smoke flows, and reports remaining risk. ## Quick Start Run Maestro QA on my app, fix the broken onboarding flow, and verify it with a targeted rerun.

Frequently Asked Questions about maestro-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Maestro QA tests on a React Native app?▼

Run the bundled helper script with your app repo path and flow directory, for example run-maestro-qa.sh with --repo pointing at the app and --flow-path set to .maestro. It produces a report-only pass with artifacts before any code changes.

How to fix a failing Maestro flow without breaking other tests?▼

Fix one verified failure at a time: classify whether it is an app bug, stale flow, or environment issue, apply the smallest change, then rerun only that single flow. Broaden to the smoke set only after the targeted rerun passes.

Does Maestro QA work with Expo apps?▼

Yes, the Skill targets both React Native and Expo apps for local mobile QA. It runs Maestro flows against the app workspace and supports tag filtering such as smoke subsets via --include-tags.

Can I preview the Maestro command without executing it?▼

Yes, pass the --dry-run flag to the helper script to print the delegated Maestro command without running it. This is useful for verifying flow paths, output directories, and report formats before a real run.

Why should I avoid rerunning the entire Maestro suite after each fix?▼

Full-suite reruns after every edit slow feedback and blur causality between fixes. The Skill reruns the single failing flow first, then the local smoke set, and only broadens to the larger suite when the scope justifies it.