I’ve written a tool for managing changelog files, called scriv. It focuses on a simple workflow, but with lots of flexibility.
I’ve long felt that it’s enormously beneficial for engineers to write about what they do, not only so that other people can understand it, but to help the engineers themselves understand it. Writing about a thing gives you another perspective on it, your own code included.
The philosophy behind scriv, and a quick list of other similar tools, is on the Philosophy page in the docs.
Scriv only does a few things now, but I’m interested to hear about other changelog workflows that could use better tooling.