canary

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps post-deploy teams catch issues early by continuously monitoring a live app for errors, regressions, and failures after deployment.

Core Features & Use Cases

  • Monitor live production URLs for console errors, performance regressions, and page failures using the browse daemon.
  • Capture periodic screenshots and compare them against pre-deploy baselines to detect visual regressions.
  • Trigger alerts when anomalies are detected to speed up triage during post-release verification.

Quick Start

Run '/canary <url>' to start a 10-minute post-deploy monitoring session for your deployed app.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor a live app for console errors and performance regressions after deployment?

Post-deploy canary monitoring detects console errors, performance regressions, and page failures on live apps. It uses the browse daemon to capture periodic screenshots and compare current behavior against baselines, raising alerts when anomalies appear.

What is post-deploy canary monitoring and when do I need it?

Post-deploy canary monitoring continuously observes live apps after release to detect issues early. You need it for validating production URLs, staging deployments, and hotfix rollouts by comparing current behavior against pre-deploy baselines.

Can I use baseline comparison to detect visual regressions on staging deployments?

Yes, baseline comparison detects visual regressions on staging deployments by capturing periodic screenshots and comparing them against pre-deploy baselines. The browse daemon runs deterministically to identify anomalies and trigger alerts.

Do I need the browse daemon to run post-release verification on production URLs?

Yes, the browse daemon is required for post-release verification on production URLs. It executes baseline comparison logic deterministically, captures periodic screenshots, and generates actionable alerts when anomalies appear.

How do I start a post-deploy monitoring session for a hotfix rollout?

Run the canary command with your target URL to start a 10-minute post-deploy monitoring session for your hotfix rollout. It monitors the live app for errors, compares behavior against baselines, and raises alerts when anomalies appear.

What are the limitations of browser-based canary monitoring for post-release validation?

Browser-based canary monitoring relies on the browse daemon and pre-deploy baselines to detect anomalies deterministically. It requires accessible URLs and existing baseline screenshots to generate actionable insights during post-release validation.