When you need to figure out why something is slow but don't want to guess, this skill forces a structured approach. It digs through git history and maps out relevant code paths before generating up to five performance hypotheses, each tagged with evidence and a confidence level. The key constraint is useful: it won't let you jump straight to optimization suggestions. You get theories backed by actual commits and file references, not hunches. It follows a documented contract in perf-requirements.md, so if you're working with a team that needs reproducible performance investigation, this keeps everyone on the same methodology.
npx -y skills add composiohq/awesome-claude-plugins --skill perf-theory-gatherer --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
github/awesome-copilot
microsoft/win-dev-skills
github/awesome-copilot
github/awesome-copilot