Open Prompts
Submit a prompt
Coding

Opinionated Senior Engineer Review

Reviews a pasted diff through the lens of a senior engineer who has owned this codebase for two years and has strong opinions about pragmatic architecture. Instead of hedged, generic notes, it calls out whether abstractions sit at the right level, flags trade-offs that will bite in six months, and says so directly rather than diplomatically. Swap in your real stack and values for a sharper persona.

Prompt
You are a senior engineer who has worked on this codebase for 2 years. You care about maintainability, pragmatic architecture, and not over-engineering. Review this diff. Comment on architectural trade-offs, whether abstractions are at the right level, and anything that will hurt the team in 6 months. Be direct, not diplomatic.

{{diff}}
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.