canary

Monitor live URLs for console errors and performance regressions after deploy.

1|2|Updated Jan 4, 2024
One-click install
npx skills add https://github.com/NaKMiers/Port4lio --skill canary-nakmiers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canary
Source: https://github.com/NaKMiers/Port4lio/tree/main/.agents/skills/canary
Command: npx skills add https://github.com/NaKMiers/Port4lio --skill canary-nakmiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-deploy canary monitoring. Watches the live app for console errors, performance regressions, and page failures using the browse daemon. Takes periodic screenshots, compares against pre-deploy baselines, and alerts on anomalies. Use when: "monitor deploy", "canary", "post-deploy check", "watch production", "verify deploy". (gstack)

Core Features & Use Cases

  • Canary-based monitoring of production apps after deployment, with automated screenshot baselines, error detection, and alert triggering.
  • Phase-based workflow: baseline capture, page discovery, quick health checks, and continuous monitoring. Use cases include verifying new deploys, catching regressions, and alerting on anomalies.
  • Use Case: After a hotfix, run canary to ensure no new console errors and perf regressions across critical pages.

Quick Start

Run /canary <url> to start 10-minute monitoring of production after deploy.

Frequently Asked Questions about canary

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

FAQPage Schema
How do I monitor production for console errors and performance regressions after a deploy?

Post-deploy monitoring detects production issues by watching a live URL for console errors and performance regressions. It takes periodic screenshots, compares them against pre-deploy baselines, and triggers alerts on detected anomalies.

What is canary-based monitoring and when do I need it?

Canary-based monitoring is a phased workflow that verifies new deploys by catching regressions early. You need it after a hotfix or deployment to ensure no new console errors or performance drops occur across critical pages.

Do I need a baseline capture to run post-deploy checks on my live app?

Yes, a baseline capture is required for meaningful comparisons. The monitoring skill operates by comparing live periodic screenshots and page health metrics against this pre-deploy baseline to identify anomalies.

How do I start continuous monitoring with anomaly alerts across configured pages?

Run a quick start command with your target URL to initiate a 10-minute monitoring session. The workflow includes page discovery, quick health checks, and continuous monitoring with automated alert triggering for anomalies.

Does post-deploy monitoring work with the browse daemon for page discovery?

Yes, the monitoring operates with the browse daemon to access the target URL. It uses this daemon to perform page discovery, take periodic screenshots, and monitor live pages for failures after deployment.