skills.rest
ingoatl
ingoatlCOMMUNITY
Explore all skills by this author →
GitHub

canary

Monitor live production URLs for console errors, performance metrics, and visual baselines.

Updated Aug 23, 2026
Search Tags:#performance#baseline#canary#production-monitoring#health-report#console-errors#post-deploy
One-click install
npx skills add https://github.com/ingoatl/propertycentral --skill canary-ingoatl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/ingoatl/propertycentral/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/ingoatl/propertycentral --skill canary-ingoatl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy canary monitoring is essential to catch issues in production before users notice. It watches the live app for console errors, performance regressions, and page failures using the browse daemon, takes periodic screenshots, and compares them against pre-deploy baselines to alert on anomalies.

Core Features & Use Cases

  • Post-deploy monitoring using the browse daemon to observe the live app, capture screenshots, and surface anomalies.
  • Baseline comparison and alerting for console errors, load times, and page failures.
  • Page discovery, configurable monitoring windows, and automated health reporting for production readiness.

Quick Start

Invoke /canary <url> to start monitoring the live site for 10 minutes after a deploy.

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 health and console errors?▼

Post-deploy monitoring captures console errors and performance metrics by observing a live production URL using the browse daemon, taking periodic screenshots to detect anomalies after a release.

How do I capture visual and performance baselines before a production deploy?▼

Baseline capture records pre-deploy screenshots and performance metrics, storing them under .gstack/canary-reports to establish a reference for detecting regressions during post-deploy monitoring.

Can I automatically discover pages to monitor for production readiness?▼

Page discovery automatically identifies relevant site URLs to monitor, enabling comprehensive health reporting and baseline comparison across an entire application after deployment.

Do I need specific environment tooling to run canary monitoring and store reports?▼

Canary monitoring requires an environment with canary tooling, target URL access, and the ability to store screenshots and baselines under the .gstack/canary-reports directory.

How do I start a quick health check after deploying to production?▼

Invoke the monitoring command with your target URL to observe the live site for ten minutes, capturing load times and page failures to alert on any immediate regressions.

Related Skills

Explore More Software Engineering Skills→
deveshkumarsdeveshkumars

canary

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

Community
Advanced
binfen1binfen1

canary

Monitor live apps for console errors, performance regressions, and page failures.

Community
Advanced
chriswesttchriswestt

canary

Monitor deployed apps for console errors, performance regressions, and page failures.

Community
Advanced
stayconnectquickstayconnectquick

canary

Monitor live applications for console errors, performance regressions, and page failures.

Community
Advanced