perf-theory-gatherer
This tool examines repository history and code to identify and link specific commits to performance bottlenecks.
Install
mkdir -p .claude/skills/perf-theory-gatherer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5801" && unzip -o skill.zip -d .claude/skills/perf-theory-gatherer && rm skill.zipInstalls to .claude/skills/perf-theory-gatherer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when generating performance hypotheses backed by git history and code evidence.Key capabilities
- →Review git history
- →Identify code paths
- →Formulate performance hypotheses
- →Link commits to regressions
- →Assign confidence scores
How it works
It analyzes git history and code structure to generate up to 5 hypotheses regarding performance bottlenecks.
Inputs & outputs
When to use perf-theory-gatherer
- →Identifying which PR introduced a performance regression
- →Analyzing historical code changes for latency patterns
- →Developing hypotheses for slow database queries
- →Connecting architecture changes to performance metrics
About this skill
perf-theory-gatherer
Generate performance hypotheses for a specific scenario.
Follow docs/perf-requirements.md as the canonical contract.
Required Steps
- Review recent git history (scope to relevant paths when possible).
- Identify code paths involved in the scenario (repo-intel or grep).
- 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.
When not to use it
- →Optimization implementation
- →General code review
Prerequisites
Limitations
- →Maximum 5 hypotheses
- →No optimization suggestions allowed
How it compares
It focuses on hypothesis generation based on historical evidence rather than providing fixes.
Compared to similar skills
perf-theory-gatherer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| perf-theory-gatherer (this skill) | 1 | 4mo | No flags | Intermediate |
| chrome-devtools | 41 | 7mo | Review | Intermediate |
| python-performance-optimization | 27 | 2mo | No flags | Intermediate |
| analyzing-logs | 14 | 27d | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by avifenesh
View all by avifenesh →You might also like
chrome-devtools
mrgoonie
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
python-performance-optimization
wshobson
Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.
analyzing-logs
jeremylongshore
Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.
redis-inspect
civitai
Inspect Redis cache keys, values, and TTLs for debugging. Supports both main cache and system cache. Use for debugging cache issues, checking cached values, and monitoring cache state. Read-only by default.
gh-fix-ci
openai
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
obsidian-performance-tuning
jeremylongshore
Optimize Obsidian plugin performance for smooth operation. Use when experiencing lag, memory issues, or slow startup, or when optimizing plugin code for large vaults. Trigger with phrases like "obsidian performance", "obsidian slow", "optimize obsidian plugin", "obsidian memory usage".