canary

Monitors deployed web apps for console errors, performance regressions, and page failures using browser automation.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/westkite1201/garden-engine --skill canary-westkite1201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/westkite1201/garden-engine/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/westkite1201/garden-engine --skill canary-westkite1201

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploys that pass CI can still break in production due to missing environment variables, stale CDN caches, or slow migrations. This Skill watches your live app in the critical first minutes after a deploy, catching issues before users do. ## Core Features & Use Cases - Continuous Post-Deploy Monitoring: Checks pages every 60 seconds for a configurable duration (1-30 minutes), comparing console errors, load times, and page availability against baselines. - Baseline Capture & Comparison: Captures pre-deploy screenshots, console error counts, and load times, then alerts only on changes — not absolute values — to avoid false alarms. - Tiered Alerting with Evidence: Classifies issues as CRITICAL (page load failure), HIGH (new console errors), MEDIUM (2x performance regression), or LOW (broken links), each backed by a screenshot. - Use Case: After deploying a new release, run the canary against your production URL for 10 minutes. If a new console error appears on /dashboard and load time doubles, you get an immediate alert with a screenshot and can choose to investigate, continue monitoring, or roll back. ## Quick Start Ask the AI to monitor https://your-app.com for 10 minutes after your deploy using the canary skill, and optionally capture a baseline first with the --baseline flag before deploying.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor my website after a deployment?

Run the canary skill with your production URL, for example /canary https://your-app.com. It checks each page every 60 seconds for 10 minutes by default, comparing console errors and load times against a baseline and alerting on persistent changes.

How do I capture a baseline before deploying?

Run /canary <url> --baseline before deploying. It records screenshots, console error counts, and page load times for each page into a baseline.json manifest, which later monitoring runs use as the comparison reference.

Can I monitor specific pages instead of the whole site?

Yes, pass --pages with a comma-separated list such as /,/dashboard,/settings. Without this flag, the skill auto-discovers the top internal navigation links and asks you to confirm which pages to monitor.

What triggers a canary alert during monitoring?

Alerts fire on changes relative to baseline: page load failures are CRITICAL, new console errors are HIGH, load times exceeding 2x baseline are MEDIUM, and new broken links are LOW. Issues must persist across two consecutive checks to avoid transient false alarms.

What are the limitations of canary monitoring?

Canary is read-only observation — it detects and reports issues but does not fix them. Without a pre-deploy baseline it acts as a simple health check rather than a regression detector, and it requires the gstack browse daemon to be built first.