Claude Code prompt

Claude Code Debug: Performance Profile

Find and verify a performance bottleneck with repository-aware safeguards.

Best tool
Claude Code
Difficulty
Beginner
Use case
Performance Profile
Prompt type
Reusable prompt

What this prompt does

Find and verify a performance bottleneck with repository-aware safeguards. It is designed for performance profile and works best with Current Claude Code model configured for the repository.

Copy-ready prompt

This is a reusable natural-language prompt for Claude Code, not a shell command. Work in the repository at [REPOSITORY_OR_PATH]. Goal: find and verify a performance bottleneck. Context: [CONTEXT]. Constraints: [CONSTRAINTS]. Definition of done: [ACCEPTANCE_CRITERIA]. Reproduce first, gather evidence, rank hypotheses, and change code only after identifying the likely cause. Read applicable CLAUDE.md guidance and use Claude Code’s repository tools and permission model; do not assume an interactive slash command or CLI flag is available. First read the repository instructions and relevant framework documentation. Preserve unrelated user changes. State assumptions, cite files and lines for findings, and ask only when a missing decision would materially change the result. Do not invent APIs, commands, flags, test results, or file contents. Deliver: baseline, instrumentation, bottleneck, and benchmark. Run the repository’s relevant formatting, lint, type, test, and build checks when authorized, and report exact results.

How to use it

Replace the bracketed variables with real context for performance profile. Attach or paste source material when available, and verify consequential facts before acting.

#claude-code#software-engineering#performance-profile#debug

Related prompts