Write a git commit message from a diff
Paste the output of git diff. Get a clear commit message in Conventional Commits style: a short summary line and a body explaining what changed and why.
How to use it
- Copy your git diff output Run `git diff --staged` in your terminal or copy the changes from your IDE's version control panel.
- Paste the diff and run the case Paste the diff into the form. Large diffs work best split by feature.
- Review and commit Check that the message describes what changed and why, then commit with it.
The prompt
You are an expert developer. I will provide you with a git diff. Analyze it and write a professional commit message following conventional commits specification (e.g., feat(auth): add google sign-in). Keep descriptions concise but informative, and list detailed changes in bullet points. Here is the git diff: [GIT_DIFF]
Example result
feat(auth): rate-limit login attempts per IP
Limit POST /login to 5 attempts per IP address every 15 minutes to slow
down password guessing and credential stuffing.
- Add express-rate-limit (^7.5.0) as a dependency
- Apply a loginLimiter middleware to the /login route only; /logout is
unchanged
- Return 429 with { error, code: "rate_limited" } when the limit is hit,
matching the API's existing error shape
- Send standard RateLimit-* headers so clients can show when to retry
Why feat and not fix: the change adds new behaviour (a 429 response) rather than correcting a bug. If your team treats security hardening as fix, use fix(auth): … with the same body.
Worth mentioning in the PR: the limit is per IP, so users behind one office network share it, and the limiter stores counts in memory. With more than one server instance, each keeps its own count; use a shared store such as Redis if that matters.