Skip to content

composio-community/awesome-claude-plugins / perf/skills/theory

perf-theory-gatherer

Verified

Use when generating performance hypotheses backed by git history and code evidence.

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.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall