Open Prompts
Submit a prompt
Coding

Performance Bottleneck Profiler

Profiles a pasted code block for real performance issues, using its execution frequency, typical data size, and your current pain point to prioritize what actually matters. - Flags O(n²) loops, N+1 queries, missing indexes, and memory/caching gaps - Ranks each finding High/Medium/Low impact with a suggested fix and expected gain - Focuses on the 20% of changes likely to deliver 80% of the speedup - Confirm suggestions with real profiling before shipping

Prompt
Analyze this code for performance issues:
{{code}}

Context:
- This runs {{execution_frequency}}
- Data size: {{data_size}}
- Current pain point: {{pain_point}}

Find:
1. Time complexity issues (O(n²) operations, unnecessary loops)
2. Database problems (N+1 queries, missing indexes, over-fetching)
3. Memory issues (large allocations, leaks, caching opportunities)
4. I/O bottlenecks (blocking calls, sequential when could be parallel)
5. Quick wins (simple changes with big impact)

For each issue:
- Impact: High / Medium / Low
- Current behavior
- Suggested fix with code
- Expected improvement

Focus on the 20% of changes that give 80% of the gains.
Download .md

Variables

Related prompts

Coding

Concurrency and race condition review

Paste code along with its concurrency model and the shared state involved for a review that skips general code-review concerns entirely and focuses only on concurrency. - Race conditions from unsynchronized read-modify-write or check-then-act patterns - Deadlock or livelock risk from lock ordering across threads or async tasks - Cleanup gaps under concurrent cancellation or failure - Each issue ships with the exact interleaving that triggers it, not a generic warning

Coding

Debug a stack trace or error message

Paste the full error message and stack trace, the code where it originates, and what you were trying to do, and get back a plain-language explanation of what the error actually means. Returns likely causes ranked from most to least probable, points to the exact lines responsible, and suggests a minimal fix or next debugging step for each — including how you might be misusing a library if the trace points there.

Coding

Git commit message writer

Takes a pasted diff plus a short note on why the change was made, and returns a commit message ready to paste into git: an imperative summary line under 72 characters, followed by an optional body covering rationale and tradeoffs. It skips line-by-line narration in favor of describing intent and impact, and flags diffs that look like they're bundling unrelated changes that should be split into separate commits.