perf-theory-gatherer
Use when generating performance hypotheses backed by git history and code evidence.
Best use case
perf-theory-gatherer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when generating performance hypotheses backed by git history and code evidence.
Teams using perf-theory-gatherer 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-gatherer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How perf-theory-gatherer Compares
| Feature / Agent | perf-theory-gatherer | 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 generating performance hypotheses backed by git history and code evidence.
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-gatherer
Generate performance hypotheses for a specific scenario.
Follow `docs/perf-requirements.md` as the canonical contract.
## Required Steps
1. Review recent git history (scope to relevant paths when possible).
2. Identify code paths involved in the scenario (repo-intel or grep).
3. Produce up to 5 hypotheses with evidence + confidence.
## Output Format
```
hypotheses:
- id: H1
hypothesis: <short description>
evidence: <file/path or git change>
confidence: low|medium|high
- id: H2
...
```
## Constraints
- MUST check git history before hypothesizing.
- No optimization suggestions; only hypotheses.
- Keep to 5 hypotheses maximum.Related Skills
perf-investigation-logger
Use when appending structured perf investigation notes and evidence.
perf-baseline-manager
Use when managing perf baselines, consolidating results, or comparing versions. Ensures one baseline JSON per version.
perf-theory-tester
Use when running controlled perf experiments to validate hypotheses.
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-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-analyzer
Use when synthesizing perf findings into evidence-backed recommendations and decisions.
learn
Research any topic online and create learning guides. Use when user asks to 'learn about', 'research topic', 'create learning guide', 'build knowledge base', or 'study subject'.
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-claude-memory
Use when improving CLAUDE.md or AGENTS.md project memory files.
sync-docs
Sync documentation with code. Use when user asks to update docs, check docs, fix stale documentation, update changelog, or after code changes.
drift-analysis
Use when the user asks about plan drift, reality check, comparing docs to code, project state analysis, roadmap alignment, implementation gaps, or needs guidance on identifying discrepancies between documented plans and actual implementation state.