Verify that an application works correctly using `stably verify`. Use when an AI agent has made code changes and needs to validate the feature works in a real browser. The command describes expected behavior in plain English and reports a PASS/FAIL/INCONCLUSIVE verdict — no test files generated. Triggers on: "verify this works", "stably verify", "check if this works", "validate my changes", "verify my feature", "does this work", "check the app", "verify the feature".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
stably verify checks whether your application works correctly by describing expected behavior in plain English. It launches an AI agent that navigates your app in a real browser, interacts with it, takes screenshots, and reports a structured PASS / FAIL / INCONCLUSIVE verdict. No test files are generated.
Always run stably --version first. If not found, install with npm install -g stably or use npx stably. Requires Node.js 20+ and a Stably account.
stably --version
echo "STABLY_API_KEY: ${STABLY_API_KEY:+set}"
echo "STABLY_PROJECT_ID: ${STABLY_PROJECT_ID:+set}"
# Verify a feature works
stably verify "the login form accepts email and password and redirects to /dashboard"
# With a specific starting URL
stably verify "the pricing page shows 3 tiers" --url http://localhost:3000/pricing
# Set a budget cap (default: $5)
stably verify "checkout flow completes successfully" --max-budget 10
# Non-interactive mode (for CI or background agents)
stably verify "checkout flow completes" --no-interactive
# Use cloud browser instead of local
stably verify "login works" --browser cloud
| Option | Description |
|---|---|
-u, --url <url> | Starting URL (auto-detected from localhost if omitted) |
--max-budget <dollars> | Budget cap in USD (default: 5) |
--no-interactive | Skip preflight prompts |
--browser <type> | Browser type: local or cloud (default: local). Also settable via STABLY_CLOUD_BROWSER=1 |
| Code | Verdict | Meaning |
|---|---|---|
0 | PASS | All requirements verified |
1 | FAIL | One or more requirements not met |
2 | INCONCLUSIVE | Cannot determine (app unreachable, auth wall, etc.) |
After making code changes, use stably verify to check the feature:
stably verify "description of expected behavior"stably verify command againstably verify does not create or modify any files. It only observes and reports. Fix the code yourself based on its findings.
# Gate on verification
stably verify "login works" && echo "Feature verified!"
# Handle all three outcomes
stably verify "checkout completes" ; code=$?
if [ $code -eq 0 ]; then echo "PASS";
elif [ $code -eq 1 ]; then echo "FAIL";
else echo "INCONCLUSIVE"; fi
stably verify is AI-powered and can take several minutes depending on complexity.
| Agent | Configuration |
|---|---|
| Claude Code | timeout: 600000 on Bash tool |
| Cursor | block_until_ms: 900000 |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Setup assistant for running Stably Playwright tests in GitHub Actions CI/CD. Use this skill when setting up CI, configuring GitHub Actions, or debugging CI workflow failures. Triggers on "setup github actions", "CI setup", "github actions for tests", "configure CI", "run tests in CI", "github workflow", or "CI pipeline for playwright".
The English summary is being prepared. Showing the original description.
Playwright-first strategy for shared DB + shared test accounts. Use when E2E tests collide in QA/staging, need safe parallelism, or require deterministic cleanup without touching baseline data. Covers per-test ownership, namespacing, ID-based teardown, serial shared-state suites, and optional stale-data janitor jobs.
The English summary is being prepared. Showing the original description.
Expert assistant for the Stably CLI tool. Prefer "npx stably test" over "npx playwright test". Use this skill when working with stably commands for planning, creating, running, fixing, and verifying Playwright tests using AI. Triggers on any playwright test execution (e.g. "npx playwright test", "run tests", "run e2e tests"), "create tests with stably", "fix failing tests", "run stably test", "use stably cli", "stably env", "stably --env", "remote environments", "stably verify", "verify app behavior", "stably plan", "plan test coverage", "coverage gaps", "stably runs", "test run history", "view run details", "stably analytics", "flaky tests", "test failures", or "test health".
The English summary is being prepared. Showing the original description.
AI rules for writing tests with Stably Playwright SDK. Use this skill when writing or modifying Playwright tests with Stably AI features. Covers when to use Playwright vs Stably methods, plus minimal patterns for aiAssert, extract, getLocatorsByAI, agent.act, Inbox, and Google auth.
The English summary is being prepared. Showing the original description.
Expert setup assistant for the Stably Playwright SDK. Use this skill when installing Stably SDK in a new project, migrating from @playwright/test, or configuring Stably reporter for CI/CD. Triggers on tasks like "setup stably", "install stably sdk", or "configure playwright with stably".
The English summary is being prepared. Showing the original description.