canary

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

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/npc-chris/dfn-discovery --skill canary-npc-chris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/npc-chris/dfn-discovery/tree/main/.agents/skills/gstack/canary
Command: npx skills add https://github.com/npc-chris/dfn-discovery --skill canary-npc-chris

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures the health of a deployed application by monitoring for console errors, performance regressions, and page failures, providing alerts on anomalies.

Core Features & Use Cases

  • Console Error Detection: Monitors live app for console errors.
  • Performance Regression Analysis: Checks for performance regressions.
  • Page Failure Alerts: Alerts on page failures.
  • Baseline Comparison: Compares against pre-deploy baselines.
  • Custom Monitoring: Allow custom monitoring duration and pages.
  • Health Report Generation: Produces a summary report of the app's health.

Quick Start

To monitor a URL after deployment, run the command: /canary <url>

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor my application for errors after a deployment?

Post-deploy application monitoring works by checking your live URL for console errors, page failures, and performance regressions. It captures screenshots and measures performance metrics to detect anomalies and generate a health report.

How do I detect performance regressions in my deployed web app?

Detect performance regressions by comparing live application metrics against a pre-deployment baseline. This baseline comparison identifies anomalies and alerts you when performance degrades after releasing new code.

What is the best way to check for console errors and page failures after releasing an update?

The best way to check for console errors and page failures is using an automated health monitoring tool that evaluates your live URL. It captures console output and page states to alert you if the deployment introduced regressions.

Do I need specific tools to run post-deploy health checks on my application?

Yes, post-deploy health checks require tools for screenshot capture and performance measurement to function properly. These dependencies enable the monitoring script to gather baseline data and detect anomalies on your live pages.

Can I customize the monitoring duration and pages tracked during application health checks?

Yes, application health checks allow custom monitoring duration and specific page targeting. You can configure these parameters to ensure the tool evaluates the most critical user flows for the required timeframe.