From dev-team-kit-fv
Monitors production after a 100% deploy completes, comparing metrics and screenshots against a pre-deploy baseline to detect silent regressions (console errors, perf drops, broken pages) during the first hours/days.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-team-kit-fv:46-post-deploy-canary-monitor [--url=https://prod.exemplo] [--baseline=path] [--interval=15m] [--duration=24h][--url=https://prod.exemplo] [--baseline=path] [--interval=15m] [--duration=24h]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Inspiracao:** [gstack/canary](https://github.com/garrytan/gstack/tree/main/canary) (MIT, Garry Tan).
Inspiracao: gstack/canary (MIT, Garry Tan). Adaptado: foca em pos-deploy (depois do 100% rollout), enquanto skill 43 cobre durante o rollout gradual.
| Skill 43 canary-deployment | Skill 45 post-deploy-canary-monitor (esta) | |
|---|---|---|
| Momento | DURANTE o rollout (0% → 100%) | DEPOIS do rollout completar (100% live) |
| Decisao | Promover ou abortar deploy | Manter producao ou rollback |
| Mecanismo | Traffic split, feature flag, blue-green | Polling de metricas + screenshot diff |
| Termina quando | 100% completo OU abortou | Janela de observacao expirou OK |
| Escalacao | (proprio rollback do canary) | Chama skill 43 (rollback) ou skill 24 (release-manager) |
Segue GLOBAL.md, policies/verification-before-completion.md (a verificacao continua
apos deploy fechar), policies/handoffs.md (escalacao pra skill 43), policies/observability-trace-tags.md.
Quando memory/constitution.md define SLOs no eixo Performance/Reliability:
url: https://prod.exemplo.com
baseline:
metrics: ./baseline/metrics-pre-deploy.json
screenshots: ./baseline/screenshots/
thresholds:
console_errors_per_min: 0 # zero tolerancia
lcp_regression_pct: 20 # >20% pior que baseline = abort
cls_regression_pct: 25
screenshot_diff_pct: 5 # >5% de pixels diferentes em paginas-chave
status_5xx_pct: 1 # >1% de respostas 5xx
window:
interval: 15m
duration: 24h
abort_after_consecutive_failures: 2
escalation:
on_abort: skill-43-rollback # ou comando manual
notify: <slack-channel | email>
Se nao houver baseline ainda, capturar antes do deploy:
# Metricas
curl -s "$URL/metrics" > baseline/metrics-pre-deploy.json
# Screenshots de paginas-chave (Playwright via anthropic-skills:webapp-testing)
# - homepage
# - 2-3 paginas mais traficadas
# - 1 fluxo critico (checkout, login, search)
A cada interval (default 15min), por ate duration (default 24h):
docs/canary-runs/YYYY-MM-DD-<release>/timeline.jsonl:{"t":"15:00","status":"ok","lcp_delta":-2,"errors":0,"screenshot_diff":0.4}
{"t":"15:15","status":"ok","lcp_delta":+5,"errors":0,"screenshot_diff":0.6}
{"t":"15:30","status":"alert","lcp_delta":+22,"errors":3,"screenshot_diff":7.2,"reason":"lcp_regression+errors"}
healthyAo detectar 2 falhas consecutivas:
docs/canary-runs/.../abort.md/run-program rollback ou skill 43 reverseNAO faz rollback automatico por default. Producao = decisao humana, salvo override explicito no input.
Ao final da janela sem aborts:
healthy em docs/canary-runs/.../verdict.mddocs/releases/<versao>.md com link pro reportdocs/canary-runs/2026-05-27-v2.19.0/
├── input.yaml # config usada
├── baseline/
│ ├── metrics.json
│ └── screenshots/
├── timeline.jsonl # 1 linha por check
├── abort.md (se houve) # detalhes do incidente
└── verdict.md # healthy | rolled-back | aborted
anthropic-skills:webapp-testing (Playwright) — captura screenshotsduration finito (24h-7d max)npx claudepluginhub felvieira/claude-skills-fv --plugin dev-team-kit-fvMonitors deployed web app URLs for post-deploy regressions including HTTP status, console errors, network failures, performance metrics (LCP/CLS/INP), content changes, and API health with alerts and looping checks.
Verifies production site health post-deploy via canary monitoring: checks HTTP status, response time, and error patterns, compares against baseline to detect regressions, and guides rollback decisions.
Monitors deployed URLs after releases: checks HTTP status, console errors, static assets, SSE streams, and performance regressions. Use after deploys, risky merges, or dependency upgrades.