---
name: Perf Theory Gatherer
slug: perf-theory-gatherer
category: Quality
description: Perf Theory Gatherer examines recent git history and relevant code paths to produce up to five evidence-backed performance hypotheses for a given scenario. Use it when you need hypotheses instead of optimizations.
github: "https://github.com/composio-community/awesome-claude-plugins/tree/master/perf/skills/theory"
language: JavaScript
stars: 1892
forks: 565
install: "npx degit https://github.com/composio-community/awesome-claude-plugins/tree/master/perf/skills/theory ~/.claude/skills/theory"
installs_to: ~/.claude/skills/theory
source_path: perf/skills/theory/SKILL.md
collection_size: 23
category_size: 1354
collection_url: "https://dirskills.com/collections/composio-community/awesome-claude-plugins"
added: 2026-08-18T06:59:19.194Z
last_synced: 2026-08-18T06:59:19.194Z
canonical_url: "https://dirskills.com/skills/perf-theory-gatherer"
---

# Perf Theory Gatherer

Perf Theory Gatherer examines recent git history and relevant code paths to produce up to five evidence-backed performance hypotheses for a given scenario. Use it when you need hypotheses instead of optimizations.

**Install:**

```bash
npx degit https://github.com/composio-community/awesome-claude-plugins/tree/master/perf/skills/theory ~/.claude/skills/theory
```

## README

# 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-map 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.