Blogmark

I asked Claude for advice on starting a fresh CHANGELOG.md file for py-vmt. It constructed a starting point that looked like the following:

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

## [0.1.0] - 2026-08-02

### Added

- `vmt start <name> [+tags]` to begin tracking a work session, with an optional
  `--at` flag to backdate the start time.
- `vmt status` to show the currently tracked session and elapsed time.
- `vmt stop` to end the active session, with a `--round` flag to round the
  duration.
- `vmt log` to display sessions tracked over the last 7 days.
- Session tags (e.g. `+python`) for categorizing tracked work.

[Unreleased]: https://github.com/jbranchaud/py-vmt/compare/v0.1.0...HEAD
[0.1.0]: https://github.com/jbranchaud/py-vmt/releases/tag/v0.1.0

The thing that immediately stuck out to me was the link to Keep a Changelog. That's a new-to-me resource. It looks well-maintained and like it is representative of standard advice useful to most OSS projects.

It reminds me a little of sites like Conventional Commits and Conventional Comments.