canary

Monitor live web applications for console errors and performance regressions.

Updated Mar 30, 2026

Search Tags:#quality assurance #error detection #performance analysis #app monitoring #post-deploy check

Ready to run

npx skills add https://github.com/joeylife94/gstack-2026-03 --skill canary-joeylife94

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/joeylife94/gstack-2026-03/tree/main/canary
Command: npx skills add https://github.com/joeylife94/gstack-2026-03 --skill canary-joeylife94

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, Glob, AskUserQuestion, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify console errors, performance regressions, and page failures in live apps after deployment, ensuring the stability of your application.

Core Features & Use Cases

Console Error Detection: Monitors for new console errors that may have been introduced during deployment.
Performance Regression Identification: Compares load times and performance metrics against pre-deploy baselines.
Page Failure Alerting: Notifies you of any page-level failures, such as timeouts or broken links.
Use Case: After deploying a new feature to your web application, use this Skill to monitor its performance and catch any issues before they impact users.

Quick Start

Run /canary <url> to start monitoring the specified URL for 10 minutes after deployment.

Frequently Asked Questions about canary

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

FAQPage Schema

How do I monitor live web apps for console errors post-deploy?▼

To monitor live web apps for console errors post-deploy, this Skill compares live application states against pre-deploy baselines using a browse daemon to detect and alert on anomalies.

What is the best way to detect performance regressions after a web deployment?▼

Detecting performance regressions after a web deployment involves comparing current load times and performance metrics against pre-deploy baselines to alert on anomalies.

How do I check for page failures and broken links after releasing a new feature?▼

Checking for page failures after releasing a new feature requires monitoring the live application for timeouts and broken links to alert on page-level anomalies.

Do I need Bash to run post-deployment checks on my web application?▼

Yes, you need Bash along with Read, Write, Glob, and AskUserQuestion tools to execute monitoring scripts and compare live states against baselines.

How long does post-deploy monitoring run when checking for app regressions?▼

Post-deploy monitoring runs for 10 minutes when checking for app regressions by comparing live states against pre-deploy baselines.

Why does my live app monitoring not catch broken links and timeouts?▼

Live app monitoring may not catch broken links and timeouts if pre-deploy baselines are not properly established for comparison.