
Canary Watch
- 4.5k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/everything-claude-code
Monitor deployed URLs for regressions across status, errors, performance, and content after deployment or risky changes.
About
Canary-watch monitors deployed URLs for regressions by checking HTTP status codes, console errors, network failures, Core Web Vitals (LCP/CLS/INP), critical content elements, and API endpoint SLAs. Developers use it post-deployment, after merging risky PRs, or following dependency upgrades. It runs in quick-check mode (single pass), continuous monitoring (N minutes over M hours), or diff mode comparing staging vs production. Critical thresholds trigger desktop notifications and optional Slack/Discord webhooks. Integrates with /benchmark for performance comparison and /browser-qa for full UI testing. Monitors 6 regression categories: HTTP status, console errors, network failures, Core Web Vitals, content integrity, API health Three monitoring modes: quick-check (single pass), continuous (interval-based over duration), diff (staging vs production comparison) Tiered alerting - critical (HTTP != 200, 5+ new errors, LCP > 4s), warning (LCP +500ms, CLS > during launch windows.
- Monitors 6 regression categories: HTTP status, console errors, network failures, Core Web Vitals, content integrity, API
- Three monitoring modes: quick-check (single pass), continuous (interval-based over duration), diff (staging vs productio
- Tiered alerting - critical (HTTP != 200, 5+ new errors, LCP > 4s), warning (LCP +500ms, CLS > 0.1), info (minor variance
- Tracks Core Web Vitals against baseline with pass/fail on LCP, CLS, INP and network request count changes
- Desktop notifications (macOS/Linux) and optional Slack/Discord webhooks for critical threshold breaches
Canary Watch by the numbers
- 4,495 all-time installs (skills.sh)
- +221 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #284 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
canary-watch capabilities & compatibility
- Capabilities
- single pass regression check on deployed url · continuous interval based monitoring over durati · staging vs production diff mode comparison · core web vitals baseline tracking (lcp, cls, inp · console error and network failure detection · critical content element validation (h1, nav, fo · api endpoint sla verification · desktop and webhook notifications
- Works with
- slack
- Use cases
- testing · devops · ci cd · debugging
- Platforms
- macOS · Linux
- Runs
- Remote server
- Pricing
- Free
npx skills add https://github.com/affaan-m/everything-claude-code --skill canary-watchAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 4.5k |
|---|---|
| repo stars | ★ 238k |
| Security audit | 2 / 3 scanners passed |
| Last updated | August 5, 2026 |
| Repository | affaan-m/everything-claude-code ↗ |
What it does
Monitor deployed URLs for regressions in HTTP status, console errors, network failures, performance metrics, content integrity, and API health after deployment or dependency upgrades.
Who is it for?
Post-deployment verification, dependency upgrade validation, continuous staging/production monitoring during launch windows.
Skip if: Local development iteration, comprehensive end-to-end UI testing, load testing.
When should I use this skill?
After deploying to production or staging, after merging risky PRs, after dependency upgrades, during launch windows.
What you get
Automated monitoring detects critical and warning-level regressions immediately; developers receive alerts and detailed canary reports.
- canary watch log
- regression report
- endpoint health status
By the numbers
- Monitors 6 regression categories (HTTP, errors, network, performance, content, API)
- Tracks 3 Core Web Vitals: LCP, CLS, INP
- Critical threshold: LCP > 4s, > 5 new errors, > 2x baseline response time
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
Forks & variants (1)
Canary Watch has 1 known copy in the catalog totaling 1.4k installs. They canonicalize to this original listing.
- affaan-m - 1.4k installs
FAQ
What triggers a critical alert?
HTTP status != 200, > 5 new console errors, LCP > 4s, or API endpoints returning 5xx responses.
How often can canary-watch check the URL?
Use --interval flag (e.g., 5m) for custom intervals; runs until stopped or --duration window expires.
Can I compare staging vs production?
Yes, use diff mode: /canary-watch --compare https://staging.myapp.com https://myapp.com
Is Canary Watch safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.