canary

Monitor live web apps for console errors and page failures after deployment.

4|2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/florianhorner/mammamiradio --skill canary-florianhorner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/florianhorner/mammamiradio/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/florianhorner/mammamiradio --skill canary-florianhorner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy monitoring of live apps to catch console errors, performance regressions, and page failures using automated checks and screenshots.

Core Features & Use Cases

  • Watches live applications after deployment to detect errors and regressions.
  • Takes periodic screenshots and compares against pre-deploy baselines to surface anomalies.
  • Alerts and surfaces actionable insights to engineers and operators.

Quick Start

Set up post-deploy canary monitoring to watch the live app for console errors and performance regressions.

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 web app for performance regressions after a production release?

Post-deploy canary monitoring detects performance regressions by running automated checks and taking periodic screenshots of the live app, comparing them against pre-deploy baselines to surface anomalies and alert engineers.

What is post-deploy canary monitoring and how does it detect console errors?

Post-deploy canary monitoring is an automated health surveillance process that watches live web applications after deployment, using automated checks to detect console errors and page failures relative to pre-deploy baselines.

Can I use automated screenshot comparisons to validate my production release?

Yes, you can validate production releases by capturing periodic screenshots of the live app and comparing them against pre-deploy baselines to identify visual anomalies, page failures, and performance regressions.

Do I need ongoing access to the live app to set up canary monitoring and alerts?

Yes, canary monitoring requires ongoing access to the live app to capture screenshots, compare baselines, run automated checks, and trigger alerts when anomalies like console errors or page failures are detected.

What's the best way to catch page failures in a web application after deployment?

The best way to catch page failures is post-deploy canary monitoring, which applies automated checks and periodic screenshots to the live app, alerting you to anomalies relative to your pre-deploy baselines.

Why does my post-deploy monitoring show performance regressions not present in staging?

Performance regressions can appear in live apps due to real-world traffic and environment differences. Canary monitoring addresses this by applying automated checks and baseline comparisons to the live app to surface these specific anomalies.