canary-watch

Monitor deployed web applications for functional and performance regressions.

1|Updated Apr 6, 2026

Search Tags:#performance #monitoring #deployment #qa #observability #regression

Ready to run

npx skills add https://github.com/vrcms/everything-qwen-code --skill canary-watch-vrcms

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: canary-watch
Source: https://github.com/vrcms/everything-qwen-code/tree/main/.qwen/skills/canary-watch
Command: npx skills add https://github.com/vrcms/everything-qwen-code --skill canary-watch-vrcms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of silent regressions after deployments or merges by providing continuous, automated monitoring of your live application.

Core Features & Use Cases

Regression Detection: Monitors HTTP status, console errors, and network failures to catch issues immediately after a release.
Performance Tracking: Compares LCP, CLS, and INP metrics against established baselines to ensure user experience remains stable.
Use Case: After pushing a critical update to production, use this skill to watch the live URL for 30 minutes to ensure no new console errors or performance degradation occur.

Quick Start

Use the canary-watch skill to monitor https://myapp.com for regressions over the next hour with a check interval of five minutes.

Frequently Asked Questions about canary-watch

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

FAQPage Schema

How do I monitor my web application for regressions after a deployment?▼

To monitor web applications for regressions after a deployment, perform periodic health checks, analyze console errors, and compare core web vitals against defined baselines to trigger alerts on critical failures.

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

Automated post-deploy regression monitoring catches silent issues after code changes by performing periodic health checks, HTTP status monitoring, and network failure analysis on your live application URL.

Can I track core web vitals like LCP and CLS against a baseline after a release?▼

Yes, you can track core web vitals by comparing LCP, CLS, and INP metrics against established baselines to ensure user experience remains stable and detect performance degradation following code changes.

How do I detect silent console errors and HTTP failures following a production merge?▼

Detect silent console errors and HTTP failures by continuously monitoring the live deployment URL for network failures and HTTP status changes, catching issues immediately after a release.

Do I need active network access to my target URL for performance monitoring?▼

Yes, active network access to the target URL is required to perform periodic health checks and gather core web vital metrics, along with configurable threshold parameters to trigger alerts.

What are the limitations of post-deploy regression monitoring for web applications?▼

Post-deploy regression monitoring requires active network access to the target URL and configurable threshold parameters, meaning it cannot analyze offline applications or trigger alerts without predefined baselines.