canary

Monitors deployed applications for console errors, performance regressions, and page failures.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill canary-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/adamtpang/summon.company/tree/main/.claude/skills/canary
Command: npx skills add https://github.com/adamtpang/summon.company --skill canary-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After deploying code, teams often lack immediate visibility into whether the live application is broken. This Skill watches the production app post-deploy, catching console errors, performance regressions, and page failures before users report them. ## Core Features & Use Cases - Post-Deploy Monitoring: Watches the live app via a browse daemon for console errors, page failures, and performance regressions. - Visual Baseline Comparison: Takes periodic screenshots and compares them against pre-deploy baselines to detect visual anomalies. - Anomaly Alerting: Alerts on detected anomalies so issues surface immediately after a release. - Use Case: After shipping a new release, run a canary check to continuously verify production health and get alerted the moment a regression appears. ## Quick Start Ask the agent to monitor the deployment and watch production for errors after the latest release.

Frequently Asked Questions about canary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor my app after a deployment?

Invoke the canary skill after deploying to watch the live app for console errors, performance regressions, and page failures. It uses a browse daemon to take periodic screenshots and compares them against pre-deploy baselines, alerting on anomalies.

What is a canary check for post-deploy verification?

A canary check continuously observes the production application right after a release to catch regressions early. This skill automates it by capturing screenshots, diffing them against baselines, and flagging errors or failures.

Can canary monitoring detect visual regressions?

Yes. The skill takes periodic screenshots of the live app and compares them against pre-deploy baselines, so unexpected visual changes after a deploy are surfaced as anomalies.

When should I run a post-deploy canary check?

Run it immediately after any production deploy or release. Trigger phrases include "monitor deploy", "canary", "post-deploy check", "watch production", and "verify deploy".

What are the limitations of screenshot-based canary monitoring?

Screenshot comparison only catches visible changes and console-level errors; it cannot detect backend logic bugs, data corruption, or issues on pages not visited by the browse daemon. Pair it with server-side logging and metrics for full coverage.