canary

Monitor live pages for errors and performance regressions after deploys.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill canary-jm199seo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/jm199seo/lostark-accessory-viewer/tree/main/.claude/skills/gstack/canary
Command: npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill canary-jm199seo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy monitoring detects production issues by watching live pages for errors, performance regressions, and failures. It helps teams verify that new code paths behave correctly in production and reduces the blast radius of incidents.

Core Features & Use Cases

  • Baseline capture and page-level health checks to spot regressions after deploys.
  • Continuous monitoring with automated alerts and structured reports for rapid response.
  • Supports selecting specific pages or pages discovered from site navigation, enabling targeted reliability checks.

Quick Start

Start by invoking /canary with a URL to begin baseline capture and ongoing monitoring.

Frequently Asked Questions about canary

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

FAQPage Schema
What is post-deploy monitoring and how does it catch production issues?

Post-deploy monitoring detects production issues by watching live pages for errors, performance regressions, and failures. It verifies new code paths in production and reduces the blast radius of incidents through continuous health checks.

How do I set up post-deploy verification for live web pages?

To set up post-deploy verification, invoke the monitoring tool with a target URL to begin baseline capture. It then performs page-level health checks and ongoing monitoring to spot regressions after deploys.

Does post-deploy monitoring require installing any external dependencies?

No external dependencies are required to run post-deploy monitoring and health checks. The tool operates independently to capture baselines, monitor live pages, and generate structured health reports.

What is the best way to get alerts for performance regressions after a production release?

The best way to catch performance regressions is through continuous monitoring with automated anomaly alerting. It watches live pages post-deploy and generates structured health reports for rapid incident response.

How does baseline capture work for post-deploy health checks?

Baseline capture records the normal state of live pages before or after a deploy. Post-deploy health checks then compare ongoing page behavior against this baseline to spot errors, performance regressions, and failures.