maestro-fix-cycle

Analyze failing Maestro YAML flows and apply iterative repairs.

1|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill maestro-fix-cycle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maestro-fix-cycle
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/maestro-fix-cycle
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill maestro-fix-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces manual debugging and cascading failures in Maestro mobile test suites by running an automated, stateful repair loop that processes failing flows one at a time, analyzes root causes, applies targeted fixes to YAML flows or app code, and verifies outcomes until the suite stabilizes.

Core Features & Use Cases

  • Stateful, resumable cycle: Persists progress, history, and learned patterns in a .maestro-cycle directory so the loop can resume after interruptions.
  • Failure analysis and targeted fixes: Parses Maestro output to identify failing steps, matches known patterns (text-mismatch, missing-testid, locale issues), and either updates flow YAML, shared sub-flows, or suggests/apply app code fixes.
  • Verification and safety limits: Re-runs flows to verify fixes, enforces max iterations per flow, prioritizes shared sub-flows to avoid cascading failures, and records all changes in an append-only history for audit.
  • Use Cases: Nightly CI repair runs for flaky UI tests, developer workflows to auto-fix regressions after UI refactors, and maintenance runs to keep large Maestro suites healthy.

Quick Start

Start maestro-fix-cycle to analyze the current failing Maestro mobile flows, apply iterative fixes one flow at a time, and continue until the suite passes.

Frequently Asked Questions about maestro-fix-cycle

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

FAQPage Schema
How do I automatically fix failing Maestro mobile test flows?▼

You can automatically fix failing Maestro mobile test flows by running a stateful repair loop that analyzes failing steps one flow at a time, applies targeted fixes to YAML or app code, and verifies outcomes until the suite passes.

Why do my React Native Maestro tests fail intermittently after UI changes?▼

React Native Maestro tests fail intermittently after UI changes due to cascading failures and mismatches like missing-testids or text-mismatches. An automated repair loop can analyze these root causes and apply iterative fixes to stabilize the suite.

Does the Maestro test repair cycle persist state if the CI run is interrupted?▼

Yes, the Maestro test repair cycle persists progress, history, and learned patterns in a .maestro-cycle directory. This allows the automated repair loop to resume from where it left off after any interruptions.

Can I run automated Maestro YAML repairs directly in my local development workspace?▼

Yes, you can run automated Maestro YAML repairs in local development. The repair cycle requires access to your apps/mobile workspace and the maestro CLI to process failing flows and apply fixes directly.

What is the best way to handle flaky UI tests in a large Maestro test suite?▼

The best way to handle flaky UI tests in a large Maestro test suite is to run nightly maintenance repair cycles that match known failure patterns, prioritize shared sub-flows, and enforce max iterations to prevent cascading failures.

What limitations exist when applying automated repairs to Maestro test flows?▼

Limitations include configurable max iterations per flow to prevent infinite loops. The repair cycle also requires the maestro CLI, access to the apps/mobile workspace, and uses an append-only history to record all changes for safety and auditing.