perf-baseline-manager

Store and compare performance baselines as single JSON files per version.

1.9k|545|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-plugins --skill perf-baseline-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perf-baseline-manager
Source: https://github.com/ComposioHQ/awesome-claude-plugins/tree/main/perf/skills/baseline
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-plugins --skill perf-baseline-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage performance baselines by consolidating results and ensuring a single baseline JSON per version, enabling consistent comparison across releases.

Core Features & Use Cases

  • One baseline JSON per version stored at {state-dir}/perf/baselines/<version>.json to guarantee versioned baselines.
  • Baseline consolidation and comparison across versions to identify regressions.
  • Use Case: In a CI pipeline, generate a baseline on each release and compare against previous versions to detect performance regressions before deployment.

Quick Start

Run the baseline manager to create and compare baselines: perf-baseline-manager --state-dir /var/state --version v1.0.0

Frequently Asked Questions about perf-baseline-manager

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

FAQPage Schema
How do I store performance baselines for CI pipeline regression testing?

Store performance baselines for regression testing by saving a single JSON file per software version at {state-dir}/perf/baselines/<version>.json. This deterministic schema placement ensures consistent baseline tracking across releases in CI pipelines.

How do I compare performance metrics across software versions to detect regressions?

Compare performance metrics across software versions by consolidating baseline JSON files and evaluating them against previous versions. This comparison process identifies performance regressions before deployment in automated workflows.

What is the JSON schema placement requirement for performance baseline versioning?

Performance baseline versioning requires a single JSON file placed deterministically at {state-dir}/perf/baselines/<version>.json. Each file records performance metrics alongside environment metadata to enforce one baseline per version.

Can I use perf-baseline-manager to track environment metadata alongside performance metrics?

Yes, perf-baseline-manager records environment metadata together with performance metrics within the versioned JSON baseline files. This ensures contextual consistency when comparing performance data across different software versions.

What is the best way to automate performance regression detection in a release workflow?

Automate performance regression detection by generating a baseline JSON on each release and comparing it against previous versions. This workflow detects regressions before deployment by enforcing one baseline per version.

Do I need dependencies to manage and compare perf baselines efficiently?

No dependencies are required to manage and compare performance baselines. The skill operates independently to consolidate results and enforce single JSON baseline files per version for regression comparison.