PR Description and Commits From a Diff

Turn a diff into a reviewable PR: what changed and why, a guide telling reviewers where to look, and conventional commit messages.

Write the PR description and commit message(s) for the changes below.

The task these changes came from: [ONE LINE: the ticket/goal, e.g. "rate-limit the public API"]
Anything the diff doesn't show: [CONTEXT: e.g. "follows up #123", "the weird part is a workaround for X"]

Diff:
"""
[PASTE git diff OUTPUT]
"""

Produce:

1. **PR title**: conventional format: type(scope): imperative summary under 70 characters. Type from: feat, fix, refactor, perf, docs, test, chore.
2. **PR description**:
   - **What & why**: 2-4 sentences: the problem, the approach, and the key decision if there was one. Written for a reviewer who hasn't seen the ticket. Not a file-by-file list: the diff already shows files.
   - **Review guide**: where to start reading, which file contains the core change, and which parts are mechanical (renames, generated files, formatting) so the reviewer can skim them.
   - **Risk & testing**: what could break, how the changes were tested (from the diff: which tests were added/changed; if none were, say so plainly rather than implying coverage).
   - **Not in this PR**: related work deliberately excluded, if the task context implies any.
3. **Commit message(s)**: if the diff contains one logical change, one conventional commit: summary line, blank line, body explaining what and why (never how; the diff shows how). If it contains multiple unrelated changes, say so, propose the commit split by file groups, and write each message.

Rules: describe only what's actually in the diff, no claiming tests, docs, or behavior that isn't there. If the diff includes a change unrelated to the stated task, flag it: reviewers hate surprises more than they hate delays.

More coding prompts

Write the commit message for this change.

Diff:
"""
[PASTE THE STAGED DIFF]
"""

Why I made this change: [THE REASON, THE TICKET, THE BUG REPORT, or "you infer it"]
Convention: [Conventional Commits / this repo's existing style, pasted below / plain]
Recent commits from this repo, to match style:
"""
[PASTE 5-10 RECENT COMMIT SUBJECT LIN

Commit Message

Write a commit message that explains why the change was made, in Conventional Commits format, split into separate commits when needed.

Codingbeginner
Help me recover from a git mistake without making it worse.

What I was trying to do: [THE GOAL]
What I ran: [THE EXACT COMMANDS, IN ORDER]
What happened instead: [THE OUTPUT OR THE STATE NOW]
Has this been pushed or shared: [YES/NO, and to which branch and whether anyone else has pulled]
Uncommitted work I cannot lose: [WHAT AND WHERE, o

Undo a Git Mistake

Recover from a bad commit, force push, wrong branch, or lost work with a reversible plan and the exact commands, explained before you run them.

Codingintermediate
Handler code, routes, and models:
"""
[PASTE THE ROUTE DEFINITIONS, HANDLERS, REQUEST AND RESPONSE TYPES, VALIDATION SCHEMAS, AND MIDDLEWARE]
"""

Generate an OpenAPI 3.1 specification from the code above.

API name, version, and base URL: [DETAILS]
Auth scheme: [BEARER JWT / API KEY / OAUTH / SESSION COOKIE, and where it is enforced]
Con

OpenAPI Spec From Code

Generate an accurate OpenAPI 3.1 spec from handler code, including error responses and auth, with gaps flagged instead of invented.

Codingintermediate

Search prompts

Find a prompt by title, description, tag, or category.