메뉴
Verify a deployed URL after a release by checking health, errors, assets, streams, and performance against a baseline.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Build Flutter APK/IPA, generate changelog, update buildlog, and commit version bump. Handles platform selection, build mode, and artifact renaming.
Build Unity APK/IPA on macOS with Unity 6.x — pre-flight checks, version bump, iOS signing params, post-build verification, buildlog, and commit.
Evidence-driven bug investigation and fix pipeline. Use when something is broken, not working, or the root cause is ambiguous.
Two independent reviewers must both approve high-stakes output before it ships, breaking the single-reviewer blind-spot problem.
Team-orchestrated feature development with parallel specialist agents. Use when building a feature that benefits from multiple agents working concurrently. You act as Product Director coordinating the team.
Interactive agent picker for composing and dispatching parallel teams. Browse available agents across domains, pick a roster, dispatch in parallel.
| name | canary-watch |
| description | Verify a deployed URL after a release by checking health, errors, assets, streams, and performance against a baseline. |
| when_to_use | Use after deploying to production/staging, after merging a risky PR, after a dependency upgrade, or to confirm a fix actually fixed it in the live environment. Triggers: "canary", "smoke test the deploy", "is prod healthy", "check the site after deploy", "post-deploy verification", "did the release break anything". Skip pre-deploy (that's local verification) and when there's no reachable URL. |
| allowed-tools | Bash Read |
Source: adapted from affaan-m/ecc
skills/canary-watch(MIT). Browser-level checks use cloakbrowser pertool-preferences.md(verify its API in-session before scripting).
Monitor a deployed URL for regressions after a release. Single-pass by default; can sustain or diff.
| # | Check | How |
|---|---|---|
| 1 | HTTP status (is it 200?) | curl -sS -o /dev/null -w '%{http_code} %{time_total}s' <url> |
| 2 | Static assets return 2xx/3xx with expected content type | HEAD each critical JS/CSS/img/font URL |
| 3 | API health within SLA | curl critical endpoints, compare latency to baseline |
| 4 | Console errors (new ones) | cloakbrowser — load the page, collect console errors |
| 5 | Key content present (h1, nav, footer, CTA) | cloakbrowser — assert selectors exist |
| 6 | Core Web Vitals (LCP/CLS/INP) vs baseline | cloakbrowser performance metrics |
| 7 | SSE / event-stream connects + first heartbeat | curl -N the stream, confirm an initial event |
HTTP/asset/API/SSE checks are pure curl. Console/content/Web-Vitals need a real browser — use
cloakbrowser, not Playwright/Puppeteer (tool-preferences.md).
canary-watch <url>canary-watch <url> --interval 5m --duration 2hcanary-watch --compare <staging> <prod>A baseline is the previous healthy run (or the staging side in diff mode). On the first run, record the observed values AS the baseline and say so — don't flag a regression with nothing to compare to.
## Canary Report — myapp.com — <date/time>
### Status: HEALTHY ✓ (or REGRESSED ✗)
| Check | Result | Baseline | Delta |
|-------|--------|----------|-------|
| HTTP | 200 ✓ | 200 | — |
| Console errors | 0 ✓ | 0 | — |
| LCP | 1.8s ✓ | 1.6s | +200ms |
| API /health | 145ms ✓ | 120ms | +25ms |
| Static assets | 42/42 ✓ | 42/42 | — |
| SSE /events | connected ✓ | connected | +80ms |
Lead with the verdict; only the regressed rows need detail. For critical regressions, state the single most likely cause and the next action (rollback? hotfix?).
production-audit — pre-launch readiness from the repo; canary-watch verifies the live result.verification-loop — local build/lint/test gate before the deploy this checks.