benchmark

To catch performance regressions in CI, you measure current metrics against a saved baseline. This skill provides repeatable performance benchmarking and outputs a before/after delta table with verdicts for pre-PR validation.

You benchmark API latency percentiles by collecting p50, p95, and p99 response times along with status codes and response sizes. This skill performs a small load test to validate your defined SLA targets.

The best way to measure Core Web Vitals is to collect real browser metrics like LCP, CLS, INP, FCP, and TTFB. This skill benchmarks page weight, bundle sizes, and request counts to detect front-end slowdowns.

Yes, you can measure build time regressions for Docker builds, type checks, and linting. This skill benchmarks development and delivery feedback loops, including cold and hot builds, to detect productivity regressions.

You store performance baselines by saving current metrics as JSON files under the .ecc/benchmarks/ directory. This enables continuous integration performance checks by providing a reference for before/after regression detection.