perf-theory-tester
Use when running controlled perf experiments to validate hypotheses.
Best use case
perf-theory-tester is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when running controlled perf experiments to validate hypotheses.
Teams using perf-theory-tester 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-theory-tester/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How perf-theory-tester Compares
| Feature / Agent | perf-theory-tester | 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 running controlled perf experiments to validate hypotheses.
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-theory-tester Test hypotheses using controlled experiments. Follow `docs/perf-requirements.md` as the canonical contract. ## Required Steps 1. Confirm baseline is clean. 2. Apply a single change tied to the hypothesis. 3. Run 2+ validation passes. 4. Revert to baseline before the next experiment. ## Output Format ``` hypothesis: <id> change: <summary> delta: <metrics> verdict: accept|reject|inconclusive evidence: - command: <benchmark command> - files: <changed files> ``` ## Constraints - One change per experiment. - No parallel benchmarks. - Record evidence for each run.
Related Skills
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.
perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
perf-analyzer
Use when synthesizing perf findings into evidence-backed recommendations and decisions.
perf-investigation-logger
Use when appending structured perf investigation notes and evidence.
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.
perf-profiler
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
perf-baseline-manager
Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.
debate
Structured AI debate templates and synthesis. Use when orchestrating multi-round debates between AI tools, 'debate topic', 'argue about', 'stress test idea', 'devil advocate'.
sync-docs
Sync documentation with code. Use when user asks to update docs, check docs, fix stale documentation, update changelog, or after code changes.
orchestrate-review
Use when user asks to "deep review the code", "thorough code review", "multi-pass review", or when orchestrating the Phase 9 review loop. Provides review pass definitions (code quality, security, performance, test coverage), signal detection patterns, and iteration algorithms.
enhance-prompts
Use when improving general prompts for structure, examples, and constraints.
validate-delivery
Use when user asks to "validate delivery", "check readiness", or "verify completion". Runs tests, build, and requirement checks with pass/fail instructions.