Conventional Commit Message Writer
Why this prompt matters
Good commit messages explain intent, not mechanics. This prompt trains the AI to focus on the why, making git history genuinely useful for debugging.
What we use it for
Developer workflow
Prompt
Analyze the following git diff and write a conventional commit message. Follow the format: type(scope): description. Types: feat, fix, refactor, docs, test, chore, perf. The description should explain WHY the change was made, not WHAT changed (the diff shows what). Keep the first line under 72 characters.
Result
fix(auth): prevent session fixation after password reset
The session token was not being regenerated after a successful password reset, allowing an attacker with a stolen session to maintain access even after the user changed their password.
Regenerates the session ID and invalidates all existing sessions for the user upon successful password change.
Good commit messages explain intent, not mechanics. This prompt trains the AI to focus on the why, making git history genuinely useful for debugging.
This prompt demonstrates a structured approach to developer workflow, producing consistent, high-quality results that can be iterated upon.