What problem does it solve?
It replaces guesswork about whether a bug reproduces or a feature works by driving the actual UI and collecting verifiable evidence, so triage, implementation, and review decisions rest on observed behavior rather than code reading alone.
Core Features & Use Cases
- Reproduce and verify modes: Confirm reported bugs on a baseline branch or validate implemented changes against expected behavior.
- Checked UI interaction loop: Find roots, observe UI state, query elements, act with expect postconditions, and wait for asynchronous transitions through pi-computer-use tools.
- Evidence-driven reporting: Aggregate verified expect verdicts, state diffs, and text extracts into triage comments, PR bodies, or review.json with explicit statuses.
- Use Case: A reviewer needs to confirm a pull request fixes a broken checkout form; the skill launches the app, drives the form end-to-end, and reports verified postconditions with the decisive on-screen text.
Quick Start
Ask the agent to verify that the reported bug on the linked issue still reproduces on the main branch using the verify-behavior skill.