Baseline comparison across CI builds for load testing

✓ Scanning codebase · ✓ Detecting product features · ✓ Growth loop analysis · → Generating prompts

---

Ddosify load-tests; comparing latency and RPS to the last main build prevents performance regressions.

We ran Skene Growth on anteon — our product manager agent that reads your code and builds a growth plan from it. It flagged that Load testing tools lack baseline comparison loops across continuous integration builds. Integrates performance testing directly into the CI/CD pipeline and prevents the deployment of performance regressions.

If useful, here's a prompt you can drop into Cursor or Claude:

Add a feature that compares the current load test results (latency, RPS) against the previous successful main-branch build, failing the PR if performance degrades by more than 10%.

Skene Growth runs in Cursor, Claude Code, or the terminal; you install it locally and it analyses the repo to suggest the next growth step.

Here's what generating the Growth Plan in our TUI looks like:

Links: Install Skene · skene-growth on GitHub · Docs

— Skene