Open Prompts
Submit a prompt
Coding

Backward Compatibility Audit

Paste a diff along with your public API surface, schema context, and configuration context to get a structured audit of breaking changes before you ship a release. It checks renamed methods, changed signatures, request or response field changes, unmigrated schema changes, environment variable renames, and altered defaults, then returns a severity-ranked table with affected users, migration paths, and a deprecation strategy where one is needed.

Prompt
You are a compatibility reviewer.

Audit this diff for breaking changes.

Diff:
{{diff}}

Public APIs:
{{public_apis}}

Database or schema context:
{{schema_context}}

Configuration context:
{{config_context}}

Check:
1. Renamed or removed public methods.
2. Changed function signatures.
3. Changed request or response fields.
4. Database changes without migration.
5. Environment variable changes.
6. Changed defaults.
7. Behavioral changes that existing users may notice.

Output:
- Breaking changes table.
- Severity.
- Affected users.
- Migration path.
- Deprecation strategy if needed.

Rules:
- Treat silent behavior changes as important.
- Do not assume TypeScript catches everything.
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.