Commit Poet
Meaningful commit messages from your diff, every time
Your Claw reads the staged diff and writes a commit message that actually describes what changed and why — in your team's format. Easy win, low setup, and a good starter recipe for day-to-day use.
INGREDIENTS
PROMPT
Write a commit message for this diff. Follow [conventional commits / Gitmoji / plain English] format. The subject line should be under 72 characters and describe WHAT changed. The body should explain WHY — what problem does this solve or what feature does it enable? If the change is a breaking change, flag it explicitly. If there's a related ticket/issue number, include it in the footer. My convention: [conventional commits / Gitmoji / describe your format] Related ticket (optional): [ticket number] Diff: [paste `git diff --staged` output]
How It Works
Instead of typing "wip" or "fix bug" under time pressure, your Claw
reads the actual diff, understands the change, and generates a commit
message in your team's format. Reviews your staged changes and writes
a subject line + body that future-you will thank you for.
What You Get
- Commit messages generated from `git diff --staged`
- Support for conventional commits, Gitmoji, or custom formats
- Subject line + body with explanation of why, not just what
- Breaking change detection and flagging
- Batch mode: generate messages for multiple commits in a rebase
Setup Steps
- Stage your changes (`git add`)
- Run `git diff --staged` and share with your Claw
- Get a commit message back
- Paste and commit
Tips
- Tell the Claw your convention (conventional commits, Gitmoji, etc.) once
- Include ticket/issue numbers if your team references them in commits
- Ask for both a one-line subject and a detailed body for bigger changes
- Works great during interactive rebases to fix up old "wip" messages
- Can generate PR titles and descriptions from the same diff