canary

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.

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.

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.

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.

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.

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.