canary

Monitor live production apps for console errors and performance regressions.

3|14|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/cegit27/moodle-proctor --skill canary-cegit27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill canary-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of undetected post-deploy issues that only surface in production, preventing small bugs and performance regressions from impacting users before you can respond.

Core Features & Use Cases

  • Live Production Monitoring: Watches the live app for console errors, performance regressions, and page failures using the browse daemon.
  • Baseline Comparison: Takes periodic screenshots and compares them against pre-deploy baselines to catch visual regressions.
  • Automated Alerting: Triggers alerts immediately when anomalies are detected, no manual checking required.
  • Use Case: After pushing a new release to your production environment, use this Skill to automatically monitor the app for 15 minutes, catch any unexpected errors or broken pages, and get alerted before users notice issues.

Quick Start

Use the canary skill to monitor the production deployment for console errors, performance regressions, and visual anomalies for 15 minutes after the latest release is live.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor my production application for errors after a deployment?

Production monitoring after a deployment is handled by using a browse daemon to watch the live app for console errors, performance regressions, and page failures, triggering alerts immediately when anomalies are detected.

What is post-deploy canary monitoring and how does it catch regressions?

Post-deploy canary monitoring is an automated verification process that compares periodic screenshots against pre-deploy baselines to catch visual regressions, detecting production stability issues before users notice them.

How can I automate release validation to catch console errors without manual checking?

Release validation is automated by deploying a browse daemon that monitors the live production environment for console errors and page failures, triggering automated alerts without requiring manual intervention.

Does automated deployment verification work for visual regressions in any web application?

Deployment verification works for any web application release workflow by taking periodic screenshots and comparing them against pre-deploy baselines to catch visual regressions in the production environment.

What is the best way to verify production stability for 15 minutes after a release goes live?

Verifying production stability is best achieved by running an automated canary monitoring process that watches the live app for 15 minutes after the release, alerting you to any unexpected errors or broken pages.

Can I trigger error alerting automatically when post-deploy anomalies are detected?

Error alerting is triggered automatically by the monitoring daemon immediately when post-deployment anomalies, console errors, or page failures are detected during the production verification window.