momentic-ai/momentic
Author, run, triage, and repair Momentic end-to-end tests for web, Android, and iOS. Use these skills when an agent must write a new test from a diff, run a suite, explain why a run failed, classify a result, or heal a broken locator.
Use Momentic's mo CLI to run and control Mo, Momentic's cloud autonomous QA agent. Use when starting or continuing Mo sessions, reading their output or status, stopping active work, answering Mo, or moving files between the local machine and Mo's hosted sandbox.
Generate an explore-prompt.md file that gives Momentic's explore agent (momentic ai explore diff / momentic ai explore latest) repo-specific context — which applications to test, the URLs tests must target, how to authenticate, where to save generated tests, and repo quirks. Use when setting up or improving the prompt file passed via --prompt-file.
Diagnose, classify, triage, and repair failing Momentic tests with MCP run tools, the Momentic CLI, and manual run artifacts. Use when a developer asks what happened on a branch, DevX or on-call asks why main is red, or the user wants to inspect classifications, de-flake quarantined or recovered tests, reduce retries, re-classify runs, run AI triage, or repair failures.
Create, run, and maintain Momentic mobile E2E tests and modules for Android and iOS. Use Momentic MCP tools for live device validation, and use direct v2 YAML edits only for high-confidence local mobile v2 changes.
Classify or explain Momentic test run results using Momentic MCP tools. Use when the user asks to categorize a failure, understand why a run failed, triage test results, or compare run results to past run results.
Improve code correctness using Momentic specs in the feature development process
Create, run, and maintain Momentic browser E2E tests and modules stored as *.test.yaml and *.module.yaml files.