stably verify checks whether your application works correctly by describing what it should do in plain English. It launches an AI agent that navigates your app with a real browser, interacts with it, takes screenshots, and reports a structured PASS / FAIL / INCONCLUSIVE verdict.
No test files are generated — it verifies and reports.
How It Works
Prerequisites
Stably CLI
Install and initialize the Stably CLI in your project.
Usage
Options
| Option | Description |
|---|---|
-u, --url <url> | Starting URL to verify against (auto-detected from localhost if omitted) |
--max-budget <dollars> | Maximum budget in USD for the session (default: 5) |
--no-interactive | Skip interactive preflight (for CI or agent use) |
Exit Codes
| Code | Verdict | Meaning |
|---|---|---|
0 | PASS | All requirements in the prompt were verified |
1 | FAIL | One or more requirements were not met |
2 | INCONCLUSIVE | Could not determine pass or fail (app unreachable, auth wall, etc.) |
Example Output
PASS
FAIL
Using stably verify with AI Agents
stably verify is especially powerful when used inside AI coding agents. The agent writes code, then runs stably verify to check if the feature actually works — creating a build-then-verify iteration loop.
Install the Skill
Install thestably-verify skill to teach your agent how to use the command:
Agent Iteration Loop
Example: Claude Code
Example: Cursor / Windsurf
Ask your agent naturally — the skill is triggered automatically:The Skill Prompt
stably-verify SKILL.md
stably-verify SKILL.md
Combining with Other Stably Commands
| Command | Purpose | When to Use |
|---|---|---|
stably verify | Verify app behavior against a description | Quick feature validation, no test files needed |
stably create | Generate Playwright test files | Building lasting regression tests |
stably test | Run existing Playwright tests | Running your committed test suite |
stably fix | Auto-fix failing tests | Tests broke and need AI-powered repair |
Build and verify
Use
stably verify to quickly check that your feature works as you build it. No test files to manage — just describe what should happen.Create lasting tests
Once the feature is stable, use
stably create to generate Playwright test files for regression coverage.CI/CD Integration
stably verify works in CI pipelines with --no-interactive: