changelog-conventions
How The Lossless Group writes and structures changelog/ entries across all repos (projects, true monorepos, pseudomonorepos). Use whenever shipping or pushing a coherent chunk of work, when scaffolding a new repo's changelog/ directory, when authoring a product release message, when the user says "log this", "write a changelog", or "ship note", or when reviewing a changelog/ file. Also fires when the user drops screenshots for an entry or the work being logged is visual — composes with prep-images-for-embed so images get CDN-hosted with real alt text without the user naming both skills. Encodes the strict frontmatter (publish, lede, ISO dates), filename pattern, "it exists" priority, the never-use-relative-image-paths rule (entries get rolled up into parent sites, so relative paths break), and the show-don't-enforce ethos.
Pinned to revision 9804a6ca9408, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/changelog-conventions/SKILL.md
- skills/changelog-conventions/references/changelog-first-development.md
- skills/changelog-conventions/references/content-repos.md
- skills/changelog-conventions/references/filename-conventions.md
- skills/changelog-conventions/references/frontmatter-spec.md
- skills/changelog-conventions/references/voice-and-shape.md
- skills/changelog-conventions/references/what-counts.md
- skills/changelog-conventions/scripts/content-stats.py
- skills/changelog-conventions/templates/entry.md
- skills/changelog-conventions/templates/release.md
Every link opens the file at its source, pinned to the revision this page describes.