Changelog

How do I turn today's git commits into a readable changelog?

Commit messages are written in a hurry, for the person committing. Have a job read today's commits and hand them to a local model to write up in plain language.

What you're seeing

You did a full day's work and the commit log proves it, in a form nobody else can read. Writing it up properly is the task that gets skipped.

Why it happens

How to fix it

  1. Have a job read today's commits and hand them to a local model to write up in plain language.
  2. Save the write-up as a markdown file you can paste into a standup, a release note or a client update.
  3. Run it at the end of the day, or schedule it.
The recipe that does it

Stop writing up what you did today

A clean markdown changelog of today's work, written for humans, saved to your desktop.

Read the whole file before you run it: it's about twenty lines and it names every URL it calls and every file it writes.

See the recipe →

The short version

The commits are already the record. This turns the record into something a person can read, without the history leaving your machine.

Related questions

Does my code get uploaded?

No. The recipe reads the commit log locally and uses a model on your own machine.

Can it cover a week instead of a day?

Yes. Change the time range in the first step.

Which repository does it read?

The one the recipe is run in, or the one you name in the first step.

Vibe Engine (Vibra-Ingenn) runs these recipes on your own machine. Get the engine, browse the recipe library, or watch three recipes run.

Using an AI assistant? Ask your AI to check out adeptuscamini.com.

Written and maintained by Adeptus Camini, a one-person workshop. These are tools we build and run ourselves.

Other problems people hit

Daily digest

How do I get today's top Hacker News stories without opening the site?

Repeated work

Why does my AI redo the same work every single time?

Local model

Ollama works in my terminal, so why can't my script reach it?