canary

Monitor production URLs post-deploy with canary checks and baseline comparisons.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/deveshkumars/Intentra --skill canary-deveshkumars
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/deveshkumars/Intentra/tree/main/canary
Command: npx skills add https://github.com/deveshkumars/Intentra --skill canary-deveshkumars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates post-deploy monitoring of a live site to surface console errors, performance regressions, and page failures using a canary approach with baseline comparisons and anomaly alerts.

Core Features & Use Cases

  • Canary baseline capture before and after deploy for reference
  • Continuous per-page monitoring with automated alerts for errors and regressions
  • Screenshots, console and performance data collection, with baseline comparisons
  • Baseline and report generation in .gstack/canary-reports for auditing and review
  • Interactive prompts and configurable page sets to tailor monitoring to production

Quick Start

Invoke /canary with a URL after deployment to start a 10-minute monitor against baselines.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor a production URL for post-deploy issues?▼

Post-deploy monitoring of a production URL catches console errors and performance regressions by capturing baseline screenshots and comparing them against live pages after deployment. You invoke the canary monitor with a specific URL to start an automated 10-minute check.

What is canary baseline comparison for production monitoring?▼

Canary baseline comparison is the process of capturing page screenshots, console, and performance data before a deploy to serve as a reference. After deploying, live production pages are monitored and compared against this baseline to detect anomalies and regressions.

Do I need a browse daemon to capture post-deploy screenshots and alerts?▼

Yes, automated post-deploy canary monitoring requires a browse daemon to capture screenshots, collect console and performance data, and compare pages against baselines. This background service enables continuous per-page monitoring and anomaly alerting.

How do I get automated alerts for console errors after a deployment?▼

Automated alerts for console errors after deployment are generated by configuring continuous per-page monitoring against a captured baseline. The canary monitor collects live console data and produces anomaly alerts when errors or performance regressions are detected.

Where are canary monitoring reports and baselines stored?▼

Canary monitoring reports and baselines are generated and stored in the .gstack/canary-reports directory. This allows for auditing and review of post-deploy screenshots, console errors, and performance comparisons after the monitoring session concludes.