Results for “performance-regression”
8 skillscanary-watch
Monitors a deployed URL after releases to catch regressions in HTTP status, console errors, network failures, performance metrics, content, API health, static assets, and SSE streams.
1
benchmark
Measures performance baselines, detects regressions before and after PRs, and compares stack alternatives.
1
benchmark
Measure performance baselines, detect regressions before and after PRs, and compare stack alternatives using browser, API, and build benchmarks.
226k
More results
canary-watch
Monitors a deployed URL for regressions after releases by checking HTTP status, console errors, network failures, performance metrics, content integrity, API health, static assets, and SSE streams.
226k
performance-profiler
Systematically profile Node.js, Python, and Go applications to identify CPU, memory, and I/O bottlenecks, generate flamegraphs, analyze bundle sizes, optimize database queries, and run load tests with k6 and Artillery.
20.4k · bundle
canary-watch
Use this skill to monitor and verify a deployed URL after releases — checks HTTP endpoints, SSE streams, static assets, console errors, and performance regressions after deploys, merges, or dependency upgrades. Smoke / canary / post-deploy verification.
0
canary-watch
Use this skill to monitor and verify a deployed URL after releases — checks HTTP endpoints, SSE streams, static assets, console errors, and performance regressions after deploys, merges, or dependency upgrades. Smoke / canary / post-deploy verification.
0
canary
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)
0