canary-watch

Monitor deployed URLs for regressions after deployments, merges, or dependency upgrades.

2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/klu-dev/porting-ecc-to-vscode --skill canary-watch-klu-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary-watch
Source: https://github.com/klu-dev/porting-ecc-to-vscode/tree/main/.github/skills/canary-watch
Command: npx skills add https://github.com/klu-dev/porting-ecc-to-vscode --skill canary-watch-klu-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of monitoring deployed URLs for regressions, ensuring stability after changes like deploys, merges, or dependency upgrades.

Core Features & Use Cases

  • Post-Deploy Monitoring: Continuously check a deployed URL for issues after deployments, merges, or dependency upgrades.
  • Customizable Watch Modes: Quick check, sustained watch, and diff mode for comparing staging vs production.
  • Alert Thresholds: Set critical, warning, and info thresholds for HTTP status, console errors, performance, and content changes.
  • Integration: Works with /browser-qa, GitHub Hooks, and CI systems for seamless integration into workflows.

Quick Start

Run the canary-watch skill with the URL you want to monitor: /canary-watch https://myapp.com

Frequently Asked Questions about canary-watch

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

FAQPage Schema
How do I monitor a deployed URL for regressions after a merge or dependency upgrade?

You can monitor a deployed URL for post-deploy regressions by running a quick check, sustained watch, or diff mode against the target endpoint to detect HTTP status, console, performance, or content changes.

What is the best way to automate post-deploy stability checks in my CI pipeline?

Automating post-deploy stability checks is achievable by integrating the monitoring process with GitHub Hooks and CI systems to trigger automated evaluations of HTTP status and performance thresholds after deployments.

Can I compare staging and production environments for content changes and console errors?

Yes, you can compare staging versus production environments using diff mode to identify content changes, console errors, and performance regressions between the two deployed URLs.

How do I set alert thresholds for HTTP status and performance monitoring?

You can configure critical, warning, and info alert thresholds for HTTP status codes, console errors, performance metrics, and content changes to receive notifications when regressions occur.

Does canary-watch work with browser automation tools for regression detection?

Yes, it integrates with browser-qa tools, GitHub Hooks, and CI systems to perform automated regression detection and post-deploy stability checks on monitored URLs.

When should I use sustained watch mode instead of a quick check for post-deploy monitoring?

Use sustained watch mode for continuous monitoring over time to catch intermittent stability issues, while a quick check validates immediate post-deploy health and HTTP status responses.