Open Prompts
Submit a prompt
Coding

Backward Compatibility Audit

Run a compatibility audit on a single diff before a library release or service deployment. - Flags removed or renamed public methods, changed signatures, and schema changes missing a migration - Catches renamed JSON fields and environment variable changes that break callers silently - Rates each issue as breaking or deprecation-worthy with a migration path - Mention your semver policy to get major-bump items flagged separately

Prompt
Analyze this diff for backward compatibility issues. Check for: removed or renamed public API methods, changed function signatures, modified database schema without migration, changed JSON field names in request/response bodies, changed environment variable names, and altered default behavior. List each breaking change with its severity (breaking vs. deprecation-worthy) and a migration path.

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