perf-baseline-manager
Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.
Best use case
perf-baseline-manager is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.
Teams using perf-baseline-manager should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/perf-baseline-manager/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How perf-baseline-manager Compares
| Feature / Agent | perf-baseline-manager | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# perf-baseline-manager
Manage baseline storage and comparison.
Follow `docs/perf-requirements.md` as the canonical contract.
## Required Rules
- One baseline JSON per version.
- Store under `{state-dir}/perf/baselines/<version>.json`.
- Record metrics + environment metadata.
## Output Format
```
baseline_version: <version>
metrics: <summary>
file: <path>
```
## Constraints
- Overwrite older baseline for the same version.
- Do not create multiple files for one version.Related Skills
perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.
perf-investigation-logger
Use when appending structured perf investigation notes and evidence.
perf-theory-tester
Use when running controlled perf experiments to validate hypotheses.
perf-profiler
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
perf-analyzer
Use when synthesizing perf findings into evidence-backed recommendations and decisions.
perf-benchmarker
Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks.
enhance-hooks
Use when reviewing hooks for safety, timeouts, and correct frontmatter.
enhance-claude-memory
Use when improving CLAUDE.md or AGENTS.md project memory files.
repo-intel
Use when user asks to "run repo intel", "generate repo map", "analyze repo", "query hotspots", "check ownership", or "bus factor". Unified static analysis - git history, AST symbols, project metadata.
enhance-agent-prompts
Use when improving agent prompts, frontmatter, and tool restrictions.
sync-docs
Sync documentation with code. Use when user asks to update docs, check docs, fix stale documentation, update changelog, or after code changes.