affaan-m/ECC

canary-watch

Review canary-watch's use cases, installation, workflow, and original source instructions.

63CollectingNetwork access

See source evidence View GitHub source

npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/canary-watch"

Source profileDocumentationCatalog only

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Limited to facts supported by the pinned source

What the pinned source establishes about canary-watch

使用此技能在部署、合并或依赖升级后监控已部署的URL是否存在回归问题。

npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/canary-watch"

Check the pinned source

The pinned source contains about 139 English words and 11 usable sections. That evidence supports a source profile, not a complete guide.

139 source words · 11 usable sections

What the source actually contains

3 verifiable source sections for canary-watch

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

使用场景

部署到生产或预发布环境后合并高风险 PR 后需要验证修复是否生效时发布窗口期间的持续监控依赖升级后

SKILL.md · 使用场景

部署到生产或预发布环境后合并高风险 PR 后需要验证修复是否生效时

02

工作原理

监控已部署 URL 是否存在回归问题。循环运行，直至手动停止或监控窗口过期。

SKILL.md · 工作原理

桌面通知（macOS/Linux）可选：Slack/Discord Webhook记录至 /.claude/canary-watch.log

03

监控内容

Review the “监控内容” section in the pinned source before continuing.

SKILL.md · 监控内容

Review and apply the “监控内容” source section.

Static permission evidence

Inspect the exact source lines that triggered a signal

These are source excerpts matched by deterministic rules, not findings of malicious behavior, safety, or actual execution.

medium · network

SKILL.md · L31

/canary-watch https://myapp.com

The documentation includes network, browsing, or remote request actions.

medium · network

SKILL.md · L37

/canary-watch https://myapp.com --interval 5m --duration 2h

The documentation includes network, browsing, or remote request actions.

Choose a different workflow

When another Skill is the better fit

canary-watch

Use this skill to monitor and verify a deployed URL after releases — checks HTTP endpoints, SSE streams, static assets, console errors, and performance regressions after deploys, merges, or dependency upgrades. Smoke / canary / post-deploy verification.

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

canary-watch

Review canary-watch's use cases, installation, workflow, and original source instructions.

A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

How do I install canary-watch?

The source record exposes this install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/canary-watch". Inspect the command and pinned source before running it.

Which permission-related actions were detected?

Static rules flagged network in the source; the page lists the matching lines and excerpts.

Repository stars

234,327

Repository forks

35,711

Quality

63/100

Source repository last pushed

2026-07-27

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

63/100

Documentation18/30

Specificity15/25

Maintenance20/20

Trust signals10/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

canary-watch by affaan-m

Use this skill to monitor and verify a deployed URL after releases — checks HTTP endpoints, SSE streams, static assets, console errors, and performance regressions after deploys, merges, or dependency upgrades. Smoke / canary / post-deploy verification.

canary-watch by affaan-m

Review canary-watch's use cases, installation, workflow, and original source instructions.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min

Canary Watch — 部署后监控

使用场景

部署到生产或预发布环境后
合并高风险 PR 后
需要验证修复是否生效时
发布窗口期间的持续监控
依赖升级后

工作原理

监控已部署 URL 是否存在回归问题。循环运行，直至手动停止或监控窗口过期。

监控内容

1. HTTP 状态 — 页面是否返回 200？
2. 控制台错误 — 是否出现之前没有的新错误？
3. 网络故障 — 是否存在失败的 API 调用、5xx 响应？
4. 性能 — LCP/CLS/INP 与基线相比是否有退化？
5. 内容 — 关键元素是否消失？（h1、导航、页脚、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:  # immediate alert
  - HTTP status != 200
  - Console error count > 5 (new errors only)
  - LCP > 4s
  - API endpoint returns 5xx

warning:   # flag in report
  - LCP increased > 500ms from baseline
  - CLS > 0.1
  - New console warnings
  - Response time > 2x baseline

info:      # log only
  - Minor performance variance
  - New network requests (third-party scripts added?)

通知机制

当超过关键阈值时：

桌面通知（macOS/Linux）
可选：Slack/Discord Webhook
记录至 ~/.claude/canary-watch.log

输出

## Canary 报告 — myapp.com — 2026-03-23 03:15 PST

### 状态：健康 ✓

| 检查项 | 结果 | 基线 | 偏差 |
|-------|--------|----------|-------|
| HTTP | 200 ✓ | 200 | — |
| 控制台错误 | 0 ✓ | 0 | — |
| LCP | 1.8s ✓ | 1.6s | +200ms |
| CLS | 0.01 ✓ | 0.01 | — |
| API /health | 145ms ✓ | 120ms | +25ms |

### 未检测到回归问题。部署状态良好。

集成

配合使用：

/browser-qa 进行部署前验证
钩子：在 git push 上添加 PostToolUse 钩子，部署后自动检查
CI：在 GitHub Actions 的部署步骤后运行

Source repo: affaan-m/ECC
Skill path: docs/zh-CN/skills/canary-watch/SKILL.md
Commit SHA: 4e973d3eaf92
Repository license: MIT
Data collected: Jul 28, 2026