canary

Monitor live app deployments for console errors, regressions, and page failures.

Updated May 14, 2026
One-click install
npx skills add https://github.com/lemig/transcriptor --skill canary-lemig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/lemig/transcriptor/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/lemig/transcriptor --skill canary-lemig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canary monitoring after deployment to quickly surface console errors, performance regressions, and page failures that affect user experience.

Core Features & Use Cases

  • Continuous post-deploy health checks detect console errors, performance regressions, and page failures using the browse daemon.
  • Periodic screenshots and baseline comparisons identify drift and anomalies, enabling rapid triage and remediation decisions.
  • Alerts provide actionable signals to guide rollback or fixes in production environments.

Quick Start

Run the canary monitor after deploying a new release to surface anomalies and alert your team immediately.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor production deployments for console errors and regressions?

Post-deploy monitoring tracks live web service deployments to detect console errors, performance regressions, and page failures. It captures console output and performance metrics to surface anomalies affecting user experience immediately after release.

What is canary monitoring and how does it detect post-release anomalies?

Canary monitoring is a post-deploy validation process that compares live application behavior against pre-deploy baselines. It detects visual regressions, page failures, and performance drift by capturing screenshots and metrics to trigger anomaly alerts.

How do I set up post-deploy health checks to guide rollback decisions?

Run post-deploy health checks immediately after releasing a new version to capture live metrics and compare them against pre-deploy baselines. These checks generate actionable anomaly alerts that signal whether to execute a production rollback or apply fixes.

Can I use visual regression monitoring for web services and APIs in production?

Yes, visual regression monitoring applies to post-release validation across web services and APIs. It uses periodic screenshots and baseline comparisons to identify visual drift and page failures during live production monitoring.

What is the best way to detect performance regressions immediately after a production deployment?

The best way to detect performance regressions is continuous post-deploy health monitoring. By capturing live performance metrics and comparing them against pre-deploy baselines, the system surfaces meaningful deviations for rapid triage and remediation.

Why do I need anomaly alerts for post-release validation in production environments?

Anomaly alerts provide actionable signals for rapid remediation during post-release validation. They immediately surface console errors and page failures detected by comparing live deployment behavior against pre-deploy baselines, preventing prolonged user experience degradation.