Write Perfect Conventional Commit Messages From Diffs

💡 Pro Tips

• •Use `git diff --staged` to get only the changes you're about to commit
• •Add context about WHY — the AI can see WHAT changed but not your reasoning
• •For large diffs, consider asking to split into multiple atomic commits

🧠 Why This Works

Good commit messages are documentation that lives forever in your git history. This prompt applies the Conventional Commits specification to your actual diffs, producing messages that are searchable, parseable by changelogs, and useful to future developers.

📅 When to Use This Prompt

Use when you've made changes and want a well-structured commit message, when you're squashing commits and need a comprehensive summary, or when your team enforces conventional commit standards and you want consistency.

🎯 What You'll Get

You'll receive a properly formatted conventional commit message with type, scope, subject line under 72 characters, and a body that explains the why—not just the what—derived directly from your code changes.