Canary Watch
- 1.4k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
This is a copy of canary-watch by affaan-m - installs and ranking accrue to the original listing.
Canary Watch is a deploy-monitoring agent skill that watches a live URL for HTTP errors, console issues, performance regressions, and content changes for developers who need regression detection immediately after a deplo
About
Canary Watch is an ECC agent skill that monitors a deployed URL for regressions after production or staging deploys, risky PR merges, dependency upgrades, or during launch windows. It runs in a loop until stopped or until the monitoring window expires, checking six signal categories: HTTP status codes, new browser console errors, failed network and 5xx API calls, LCP/CLS/INP performance against baseline, missing critical DOM elements such as h1, nav, footer, and CTA, and API endpoint health within SLA. Quick-check mode runs a single pass and reports results via `/canary-watch https://myapp.com`, while continuous mode rechecks every N minutes for M hours with `--interval 5m`. Developers reach for Canary Watch when they need automated post-deploy confidence without standing up a full APM stack.
- Monitors 8 distinct signals including HTTP status, console errors, network failures, Core Web Vitals, content integrity,
- Supports Quick check (single pass) and Sustained watch (interval + duration) modes
- Runs post-deploy, after PR merges, dependency upgrades, or during launch windows
- Compares against baseline to detect regressions
- Hard-gate verification before declaring a release complete
Canary Watch by the numbers
- 1,386 all-time installs (skills.sh)
- +83 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill canary-watchAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 238k |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
How do you monitor a URL after deploy?
Automatically monitor a live URL for HTTP errors, console issues, performance regressions, and content changes right after a deploy or risky merge.
Who is it for?
Developers who just deployed or merged a risky PR and need automated live URL regression checks during a launch window.
Skip if: Teams needing long-term infrastructure monitoring, log aggregation, or alerting platforms instead of short post-deploy canary verification.
When should I use this skill?
A production or staging deploy, risky merge, or dependency upgrade completes and the live URL must be watched for regressions.
What you get
Regression reports covering HTTP status, console errors, network failures, Core Web Vitals deltas, missing DOM elements, and API health.
- Post-deploy regression report
- Continuous monitoring log
By the numbers
- Monitors six regression signal categories on deployed URLs
- Supports quick-check and continuous interval-based monitoring modes
Files
カナリアウォッチ — デプロイ後の監視
使用時期
- 本番またはステージングへのデプロイ後
- 危険なPRをマージした後
- 修正が実際に修正されたことを確認したい場合
- ローンチウィンドウ中の継続的監視
- 依存関係アップグレード後
動作方法
デプロイされたURLの回帰を監視します。停止されるか監視ウィンドウが期限切れになるまで、ループで実行されます。
監視内容
1. HTTPステータス — ページは200を返していますか？
2. コンソールエラー — 以前なかった新しいエラーはありますか？
3. ネットワークの障害 — 失敗したAPIコール、5xx応答？
4. パフォーマンス — LCP/CLS/INPの回帰対ベースライン？
5. コンテンツ — 主要な要素は消えましたか？（h1、nav、footer、CTA）
6. API健康 — 重要なエンドポイントはSLA内で応答していますか？監視モード
クイックチェック（デフォルト）：シングルパス、レポート結果
/canary-watch https://myapp.com継続監視：N分ごとにM時間チェック
/canary-watch https://myapp.com --interval 5m --duration 2h差分モード：ステージング対本番を比較
/canary-watch --compare https://staging.myapp.com https://myapp.com警告しきい値
critical: # 即座の警告
- HTTPステータス != 200
- コンソールエラー数 > 5（新しいエラーのみ）
- LCP > 4s
- APIエンドポイントは5xxを返す
warning: # レポートで報告
- LCP ベースラインから > 500ms増加
- CLS > 0.1
- 新しいコンソール警告
- レスポンス時間 > 2xベースライン
info: # ログのみ
- マイナーパフォーマンス分散
- 新しいネットワークリクエスト（サードパーティスクリプトが追加された？）通知
重大なしきい値を超えたとき：
- デスクトップ通知（macOS/Linux）
- オプション：Slack/Discord Webhook
~/.claude/canary-watch.logにログ
出力
## Canary Report — myapp.com — 2026-03-23 03:15 PST
### Status
- ✓ HTTP 200
- ✓ No critical errors
- ✓ LCP within SLA (1.8s)
### Diffs from Baseline
- CLS: 0.08 (↓ 0.02)
- Response: 245ms (↑ 12ms, OK)
- Network: 42 requests (↑ 3, investigate third-party?)統合
/benchmarkとペアリングしてパフォーマンス比較/browser-qaとペアリングして完全なUIテスト- CI/CDパイプラインに組み込んでオートメーション監視
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3kHow it compares
Pick Canary Watch for short post-deploy URL regression sweeps rather than permanent production observability platforms.
FAQ
What does Canary Watch check on a deployed URL?
Canary Watch checks HTTP status, browser console errors, failed network and 5xx calls, LCP/CLS/INP performance against baseline, missing h1/nav/footer/CTA elements, and critical API endpoint health within SLA.
How do you run a quick Canary Watch check?
Canary Watch quick-check mode runs a single monitoring pass with `/canary-watch https://myapp.com` and returns a regression report without entering a continuous loop.