canary

Monitor console errors, network requests, performance metrics, and visual layout after deployment.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/himes19/pulsevolt-infra --skill canary-himes19
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/himes19/pulsevolt-infra/tree/main/skills/gstack/canary
Command: npx skills add https://github.com/himes19/pulsevolt-infra --skill canary-himes19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy monitoring helps catch issues that only appear under real user traffic, including errors, performance regressions, and visual regressions.

Core Features & Use Cases

  • Post-deploy health checks: continuously monitor console errors, network failures, page performance, and visual layout after deployment.
  • Anomaly detection: compare iterations to baseline and alert when new errors or performance regressions appear.
  • Output: provide a concise health report showing duration, checks, anomalies, and status.

Quick Start

Run the canary after deployment to start a 30-minute monitoring loop that checks for console errors, network failures, and performance changes.

Frequently Asked Questions about canary

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

FAQPage Schema
What is post-deploy anomaly detection and when do I need it?

Post-deploy anomaly detection catches issues appearing under real user traffic by monitoring console errors, network failures, and performance regressions within a 30-minute window after deployment.

How do I run health checks after deploying to production?

Run post-deploy health checks by starting a 30-minute monitoring loop that exercises 2-3 critical flows, checking console errors, network requests, performance metrics, and visual layout every 2-5 minutes.

Can I monitor visual layout and network requests in a production-like environment?

Yes, you can monitor visual layout and network requests by operating in production-like environments with real-user traffic to detect anomalies and compare iterations against a baseline.

What's the best way to detect performance regressions after a release?

Detect performance regressions by running a fixed monitoring cadence that compares post-deploy iterations to a baseline, alerting when new console errors or performance drops appear in the health report.

Does post-deploy monitoring require real-user traffic to detect anomalies?

Yes, post-deploy monitoring operates in production-like environments with real-user traffic to effectively catch issues that only appear under real load, exercising critical flows during the monitoring window.

What limitations should I expect with a 30-minute post-deploy monitoring window?

The 30-minute post-deploy monitoring window limits detection to immediate anomalies within that timeframe, using a fixed cadence and focusing on 2-3 critical flows rather than long-term performance trends.