canary

Monitor deployed web apps for console errors, performance regressions, and page failures.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/legotec73/gstack --skill canary-legotec73
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/legotec73/gstack/tree/main/canary
Command: npx skills add https://github.com/legotec73/gstack --skill canary-legotec73

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy canary monitoring catches production issues early by watching live app behavior, spotting console errors, regressions in performance, and page failures, and by capturing periodic visuals for baseline comparison.

Core Features & Use Cases

  • Canary monitoring using the browse daemon to surface anomalies after deployments.
  • Periodic screenshots and baseline comparisons to detect regressions.
  • Alerting and reporting when anomalies are detected to guide quick remediation.

Quick Start

Run /canary <url> after deploy to start a 10-minute monitor of the live site.

Frequently Asked Questions about canary

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

FAQPage Schema
What is post-deploy canary monitoring and how does it catch production issues?

Post-deploy canary monitoring detects production issues by watching live app behavior for console errors, performance regressions, and page failures, then capturing periodic screenshots for baseline comparisons to alert on anomalies.

How do I start canary monitoring of a live web app after a rollout?

To start canary monitoring, run the /canary command with your target URL after a deployment to initiate a 10-minute monitor that surfaces anomalies and captures periodic screenshots for baseline comparison.

Does canary monitoring work with feature flags and hotfixes?

Canary monitoring works for post-deploy verification across web apps and services, especially during rollouts, feature flags, or hotfixes where early anomaly detection matters for live production environments.

What's the best way to detect performance regressions after a production deploy?

The best way to detect performance regressions is using canary monitoring with a browse daemon to capture visuals, compare against pre-deploy baselines, and alert on anomalies with actionable remediation guidance.

Do I need a browse daemon to take baseline screenshots for anomaly detection?

Yes, canary monitoring relies on the browse daemon to capture periodic visuals and compare them against pre-deploy baselines to detect page failures and surface anomalies after deployment.