auto-canary

Runs post-deploy build, E2E, and browser health checks with PASS/WARN/FAIL verdicts.

111|73|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/autopus-ai/autopus-adk --skill auto-canary-autopus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-canary
Source: https://github.com/autopus-ai/autopus-adk/tree/main/.omp/skills/auto-canary
Command: npx skills add https://github.com/autopus-ai/autopus-adk --skill auto-canary-autopus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a deployment, teams need a fast, repeatable way to confirm the build, endpoints, and browser surface are operational without running a full QA suite. This Skill automates that smoke-check gate and records the latest status for later comparison. ## Core Features & Use Cases - Sequential health checks: Runs build verification, E2E tests, and browser health checks declared in .autopus/project/canary.md, then issues a PASS/WARN/FAIL verdict. - Watch and compare modes: Repeats checks on a configurable interval (--watch, default 5m, max 30m) and compares results against a previous run via --compare <commit>. - Persistent status: Writes the latest verdict to .autopus/canary/latest.json so pipelines and dashboards can consume the current deployment state. - Use Case: After deploying a staging build, run /auto canary --url https://staging.example.com to confirm the build, endpoints, and browser surface are healthy before promoting to production. ## Quick Start Ask the agent to run the canary health check against your deployed URL, for example: run /auto canary --url https://staging.example.com and report the verdict.

Frequently Asked Questions about auto-canary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a post-deploy smoke test on a staging URL?▼

Run /auto canary --url https://your-staging-url to execute build, E2E, and browser health checks against that target. The URL flag overrides the browser target declared in canary.md, and the result is saved to .autopus/canary/latest.json.

What is the difference between auto canary and auto qa?▼

auto canary is a lightweight post-deploy smoke and status gate producing a PASS/WARN/FAIL verdict. Use auto qa when you need QAMESH manifests, redacted artifacts, run indexes, or evidence-backed browser, desktop, and mobile user journeys.

How do I monitor deployment health continuously?▼

Use the --watch flag with an interval, such as /auto canary --watch 5m, to repeat the health checks on a schedule. The default interval is 5 minutes and the maximum allowed is 30 minutes.

What happens if the canary.md configuration file is missing?▼

The skill explicitly reports that the configuration is absent and directs you to run /auto setup. The canary.md file declares the build, smoke, endpoint, and browser targets the checks depend on.

How does the PASS, WARN, or FAIL verdict get decided?▼

PASS requires a successful build, all E2E tests passing, and no critical browser errors. WARN means the build succeeded but some E2E tests failed or non-critical browser warnings appeared. FAIL means the build failed or critical E2E or browser errors occurred.