Verified:GitHub

canary

Detect post-deploy production regressions by monitoring a live URL for errors and performance changes.

6|2|Updated Oct 18, 2021

Search Tags:#visual diff #performance regression #canary monitoring #production deploy #console error detection #release reliability

Ready to run

npx skills add https://github.com/jerrywu001/jerrywu001 --skill canary-jerrywu001

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/jerrywu001/jerrywu001/tree/main/.claude/skills/canary
Command: npx skills add https://github.com/jerrywu001/jerrywu001 --skill canary-jerrywu001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you detect real-world production problems that slip past CI by watching the live site right after a deploy for errors, broken pages, and performance slowdowns.

Core Features & Use Cases

Post-deploy visual and console monitoring: Repeatedly checks pages and captures evidence with screenshots and console error output.
Baseline-based regression detection: Compares current behavior to pre-deploy (or reference) screenshots and performance numbers to flag changes.
Alerting and reporting: Surfaces critical/high issues immediately and produces a health report with artifacts you can review.

Quick Start

Run /canary <url> --baseline before deploying, then deploy and run /canary <url> to monitor the site for about 10 minutes.

Frequently Asked Questions about canary

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

FAQPage Schema

How do I detect production regressions after a deploy?▼

Detect production regressions after a deploy by continuously monitoring a live URL for console errors, page failures, and performance changes against a pre-deploy baseline. This Skill captures screenshots and compares performance metrics to flag real-world issues that slipped past CI.

What is post-deploy canary monitoring and how does it work?▼

Post-deploy canary monitoring works by repeatedly checking live pages after a release to capture evidence via screenshots and console error output. It compares current behavior against a reference baseline to immediately surface critical issues and generate a saved health report for triage.

How do I set up a baseline for visual diff regression detection?▼

Set up a baseline for visual diff regression detection by running a health check against your target URL before deploying. This captures reference screenshots and performance numbers, which the monitor then compares against the live site post-deploy to flag visual and performance changes.

Can I monitor specific pages for console errors during a release verification?▼

Yes, you can monitor specific pages for console errors during release verification. The Skill supports optional page selection, allowing you to target critical user flows for post-deploy canary checks and quick one-pass health checks to ensure release reliability.

What's the best way to catch performance regressions minutes after a production deploy?▼

The best way to catch performance regressions minutes after a production deploy is continuous live URL monitoring with baseline comparison. By capturing screenshots and tracking performance numbers against a pre-deploy reference, you get immediate alerts for critical slowdowns and page failures.

Do I need screenshots to run a post-deploy health check?▼

Yes, screenshots are required to run a post-deploy health check. The regression detection process relies on screenshot capture plus baseline comparison to identify visual diffs and page failures, producing a saved report with artifacts for evidence-based triage.