canary

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy canary monitoring detects production issues by watching the live app for console errors, performance regressions, and page failures. It captures periodic screenshots, compares against pre-deploy baselines, and alerts on anomalies.

Core Features & Use Cases

  • Monitor live app for console errors, performance regressions, and page failures using the browse daemon.
  • Take periodic screenshots and compare against baselines to detect regressions.
  • Alert on anomalies and guide actions after adeploy to protect release quality.
  • Use after deploys to verify stability across critical pages and paths.

Quick Start

Run the canary after deploying to start monitoring the live app for 10 minutes and compare against baselines.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor for production regressions after a deploy?

Post-deploy canary monitoring detects production regressions by watching the live app for console errors, performance drops, and page failures. It captures periodic screenshots and compares them against pre-deploy baselines to verify stability across critical pages.

What is canary monitoring and how does it work?

Canary monitoring is a post-deploy verification process that uses a browse daemon to watch a live app. It compares current periodic screenshots and performance metrics against pre-deploy baselines to detect console errors, page failures, and performance regressions.

How do I detect console errors and page failures in production?

You can detect console errors and page failures by running a post-deploy canary monitor. It uses a browse daemon to watch the live app, capturing screenshots and comparing them against baselines to alert on any detected anomalies.

Do I need pre-deploy baselines to monitor production stability?

Yes, baseline captures are required for post-deploy canary monitoring. The alert logic compares current live app results, such as periodic screenshots and performance metrics, against these pre-deploy baselines to accurately detect regressions and trigger alerts.

How long does post-deploy canary monitoring take to verify stability?

Post-deploy canary monitoring runs for 10 minutes after a deploy to verify stability. During this period, it watches the live app for console errors and performance regressions, comparing periodic screenshots against baselines to detect anomalies.

Can I use canary monitoring to check critical paths after deploys?

Yes, post-deploy canary monitoring is used after deploys to verify stability specifically across critical pages and paths. It watches the live app for performance regressions and page failures using baseline comparisons to protect release quality.