canary

Monitor production pages post-deploy for console errors, performance regressions, and page failures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy issues can slip through CI and crash production; this skill watches the live app after deploy, captures baselines, and alerts on anomalies.

Core Features & Use Cases

  • Baseline capture and comparison to detect regressions.
  • Page discovery and targeted monitoring across multiple routes.
  • Continuous monitoring with configurable duration and alerting for console errors, performance, and page failures.

Quick Start

Run /canary <url> to start a 10-minute post-deploy monitoring session.

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 immediately after a deployment?

Post-deploy monitoring captures baseline references and alerts on console errors, performance regressions, and page failures across specified routes. Run /canary <url> to start a 10-minute monitoring session that detects anomalies in the live app.

What is the best way to catch console errors and page failures in production after a release?

A browse daemon watches the live app after deploy, capturing baselines and alerting on anomalies like console errors and page failures. It applies continuous monitoring across specified pages for a configurable duration to catch issues that slipped through CI.

How do I capture and compare performance baselines to detect regressions post-deploy?

Baseline capture records initial performance metrics for comparison after deployment. The browse daemon monitors specified pages against these baselines, alerting you when performance regressions or page failures occur during the monitoring window.

Can I select specific pages or routes for continuous production monitoring?

Yes, page discovery and targeted monitoring allow you to select specific routes for surveillance. The browse daemon applies continuous monitoring with configurable duration across these targeted pages, alerting on any detected console errors or page failures.

Do I need a browse daemon to set up post-deploy alerting for performance issues?

Yes, the browse daemon is required for post-deploy monitoring. It works together with baseline references, configurable duration, page targets, and alerting flows to notify you on anomalies detected across the live application after deployment.