Issue 09 · 13 Sep 2026 · Easy · Free
Commit Message Fortune
You know the change worked and you still type 'fix stuff' because writing the real sentence feels longer than the fix.
Paste what the diff did. Get a Conventional Commit a teammate can trust, and a fortune you will not push.
- Category
- Fun & Weird
- Runs in
- ChatGPT
- Claude
- Gemini
What you put in and what you get out
You put in
Say what the diff did. One to five lines: the behavior that changed, the test you ran, and anything the message must not include. You do not need to paste a secret or a customer name to get a good subject.
Agent
Commit Message Fortune
You get out
The cut. No customer name, no ticket you do not have, subject short enough to read in git log.
Sample you can paste
Repo: billing API. The diff stops trusting body.total and sums the cart on the server again. Tests: the new test posts a fake total of 1 and expects the stored total to match the cart. No ticket number. No breaking API change. Do not mention the customer's name anywhere.
Share this agent
Commit Message Fortune — You put in Repo: billing API.. You get out The cut. Free from One Agent a Day.
30-second demo
0:00
The change
Checkout sums the cart on the server again and ignores a client total of 1.
How it works
The useful output is a Conventional Commit a teammate can trust next month. The fortune is the joke you are not allowed to push. You paste what the diff did and what it must not mention. You commit only the plain message.
The joke can tease the code. It cannot tease a person, a customer, or a group. If the only funny version needs a name you were told to leave out, the fortune is one dry sentence and the plain message still ships.
Subject line under 72 characters. Body only if the reason is not obvious from the subject. No ticket number you did not provide.
Use it
Step 1
Say what the diff did
One to five lines: the behavior that changed, the test you ran, and anything the message must not include. You do not need to paste a secret or a customer name to get a good subject.
Step 2
Paste the prompt
You get two outputs. The first is the message you may commit. The second is a fortune-cookie version that stays in the chat.
Step 3
Commit the plain one
Copy the Conventional Commit. If the subject wraps past 72 characters, shorten it before you commit. Leave the joke out of git log.
Step 4
Keep the fortune if it helps you remember
The joke is for you. If it names a person, a customer, or a slur, it failed. Throw it away and keep the plain message.
Prompt
commit-message-fortune.prompt.txt
You write two commit messages from a description of a diff. One is safe to commit. One is a fortune cookie that must not be committed.
INPUTS
- What changed, in the author's words.
- Test they ran, if any.
- Forbidden: names, customers, or tickets they said to leave out.
RULES
- The committable message uses Conventional Commits: feat, fix, docs, refactor, test, chore. Pick one.
- Subject is imperative, no period, 72 characters or fewer.
- Body is optional and only for the reason. Do not restate the subject.
- Do not invent a ticket, a co-author, or a breaking-change footer unless they said so.
- The fortune is one or two sentences. It may tease the code. It may not tease a person's body, identity, family, or any name on the forbidden list.
- If you cannot be funny without breaking that rule, write a flat fortune: "The diff did the thing. You may go."
- Label the fortune DO NOT COMMIT.
OUTPUT
## Commit
The message inside a fence.
## Fortune
DO NOT COMMIT
The joke.
## Why this type
One line on the Conventional Commit type you picked.Related agents
Tomorrow's drop
Get the next agent in your inbox
One email when the drop goes up. No digest, no course. Unsubscribe whenever the provider lets you.
Pro and custom
€9/month when Pro opens
Early look at the next drop, a better archive, and the occasional agent that does not fit the public mix. The daily agent stays free. A custom build is €49–199. Nothing is charged from this form.
Join the Pro waitlist