Perf Theory Gatherer
- 2 installs
- 931 repo stars
- Updated July 26, 2026
- avifenesh/awesome-slash
perf-theory-gatherer is a skill that generates up to five performance hypotheses for a scenario, backed by git history and code evidence.
About
This skill generates performance hypotheses for a specific scenario, grounded in git history and code paths. A developer uses it at the start of a perf investigation to enumerate what might be slow and why. It reviews recent git history, identifies involved code paths, and produces up to five hypotheses each with evidence and a confidence level, without suggesting optimizations.
- Generates performance hypotheses backed by git history and code evidence
- Requires checking recent git history before hypothesizing
- Produces up to 5 hypotheses with evidence and confidence, no fixes
Perf Theory Gatherer by the numbers
- 2 all-time installs (skills.sh)
- Ranked #467 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
perf-theory-gatherer capabilities & compatibility
- Capabilities
- hypothesis generation · git history analysis · debugging
- Works with
- github
- Use cases
- debugging · research
What perf-theory-gatherer says it does
Generate performance hypotheses for a specific scenario.
MUST check git history before hypothesizing.
No optimization suggestions; only hypotheses.
npx skills add https://github.com/avifenesh/awesome-slash --skill perf-theory-gathererAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 931 |
| Last updated | July 26, 2026 |
| Repository | avifenesh/awesome-slash ↗ |
What it does
Generate up to five evidence-backed performance hypotheses for a scenario from git history and code paths.
Who is it for?
Developers starting a performance investigation who need structured, evidence-backed hypotheses to test.
Skip if: Proposing optimizations or fixes, which the skill explicitly excludes.
When should I use this skill?
You are generating performance hypotheses backed by git history and code evidence.
What you get
Up to five hypotheses, each with an evidence pointer and confidence level, ready to test.
- ranked hypothesis list with evidence and confidence
By the numbers
- up to 5 hypotheses maximum
Files
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
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512FAQ
How many hypotheses does it produce?
Up to five hypotheses, each with evidence and a confidence level.
Does it suggest fixes?
No, it only produces hypotheses and explicitly avoids optimization suggestions.