maestro-testgen
A developer tool skill that takes a code diff or plain description of a UI change and generates both a step-by-step manual test case and a Maestro YAML automation script, but only after deciding whether the change actually affects what users see on screen.
This tool is designed to help software developers write UI regression tests, which are checks that verify app interfaces still behave correctly after code changes. You give it either a code diff (a summary of what changed in the code) or a plain description of what changed, and it figures out whether the change is likely to affect what users see on screen.
The core workflow follows a deliberate order. First, the tool decides whether a change is actually a user-visible UI behavior or purely internal logic like sorting or formatting. If the change is UI-relevant, it writes a manual test case document that you or a tester can follow step by step. Only after that does it decide whether the test can be automated. If the answer is yes, it produces a Maestro YAML file, which is a machine-readable script that drives a real mobile or web app through the test steps.
Maestro is an open-source tool for writing mobile UI automation tests. This skill generates Maestro scripts only when it has enough reliable information to do so, such as stable element selectors and no coordinate-based tapping. It will not produce a script when the evidence is insufficient.
When a device is available and connected, the skill can run the generated YAML automatically, capture an HTML report, and save screenshots into the project's qa directory. If no device is connected, it prints the command you would need to run manually and prompts you to start a device.
Installation works either as a plugin, which automatically registers the Maestro server, or as a manual file copy. The skill targets Android, iOS, and Web projects. The repository has no primary programming language listed.
Where it fits
- Automatically generate a Maestro UI test script from a pull request diff to catch regressions before merging, only when the change is actually user-visible.
- Produce a manual step-by-step test document for a UI change when automation is not reliable due to unstable selectors or coordinate-based tapping.
- Run generated Maestro tests against a connected device from within the skill, then save the HTML report and screenshots to the project qa directory.