changelog-conventions

What problem does it solve?

This Skill solves the problem of inconsistent, unstructured changelog entries that fail to serve external audiences, contributors, or cross-repo aggregated feeds, eliminating ad-hoc formatting decisions and wasted revision time for teams maintaining multiple repositories.

Core Features & Use Cases

• Cross-repo consistent conventions: Enforces standardized frontmatter fields, ISO-date filename patterns, and body structure for changelog entries across standalone projects, true monorepos, and pseudomonorepos.
• Audience-aligned content structure: Provides a canonical body shape (lede, Why Care?, What's New?) that serves both general external audiences and internal engineering teams without reformatting.
• Comprehensive reference and templates: Includes ready-to-use templates for standard entries and product releases, plus reference docs covering frontmatter rules, filename conventions, voice guidelines, and heuristics for what qualifies as changelog-worthy work.
• Use Case: A team shipping a new feature across a pseudomonorepo with multiple submodules can use this Skill to write a single changelog entry that renders correctly in the submodule's local feed, the parent pseudomonorepo's rolled-up changelog, and the org-wide Lossless Changelog umbrella view.

Quick Start

Use the changelog-conventions skill to write a new changelog entry for the feature you just shipped, following the required frontmatter fields and body structure guidelines.