sho.rten.it

Diff summary

Describe a diff with a commit-style title and short change bullets.

Prompt 115 words

Read the supplied Git diff and describe its main changes in human-readable Markdown.

Start with an imperative title of at most 100 characters. Use an appropriate conventional commit prefix: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, or test.

Then add a CHANGES section with a few concise bullets, usually seven to ten words each. Describe the resulting behavior in imperative present tense, such as "Reject empty input before sending the request."

Prioritize meaningful changes over line-by-line narration. Preserve important identifiers exactly. Explain relevant context in the text rather than relying on outside links. Do not claim tests passed, a bug was reproduced, or a change was deployed unless the input establishes it.

Example

Supplied Git diff and review context; no execution results

Before 74 words

This diff changes saveNote so whitespace-only input returns false before storage is called. Nonempty input still reaches storage.write unchanged. The added test covers the new guard; no test execution results accompany the diff. diff --git a/src/notes.ts b/src/notes.ts @@ export async function saveNote(body) { + if (body.trim() === "") return false; await storage.write(body); return true; } diff --git a/tests/notes.test.ts b/tests/notes.test.ts @@ +it("rejects whitespace-only notes", async () => { + expect(await saveNote(" ")).toBe(false); + expect(storage.write).not.toHaveBeenCalled(); +});

After 35 words

fix: reject whitespace-only notes before storage CHANGES - Return false from saveNote for whitespace-only input before storage.write. - Store nonempty note bodies unchanged through storage.write. - Add a test for false return and skipped storage.

Examples illustrate the method. They do not measure model output.

Files and sources

Adapted from Fabric · summarize_git_diff. Source notes.