How to Write Commit Messages Future You Will Thank You For

The diff shows what changed. The message explains why.

[ essay ]

Commit messages are async communication with future teammates — including you.

Use conventional prefixes: feat, fix, refactor, chore, docs. They enable changelog automation and quick scanning.

Body text answers: what problem? why this approach? what to watch in prod?

Avoid “fixed stuff” and “wip” on main. If work is incomplete, stay on a branch.

Breadcrumbs beat archaeology. One minute writing saves an hour guessing.

— JV · Dark Heart Labs.