docs-changelog

Automating changelog generation from GitHub releases requires parsing raw release data, categorizing highlights, and formatting PR references into standard or preview markdown files. This skill standardizes that workflow by automatically structuring release notes with correctly linked PR references.

Updating documentation changelogs for standard and preview releases involves routing entries to specific files. Standard releases update latest.md and index.md, while preview releases update preview.md, ensuring categorized highlights and linked PR references are formatted correctly.

Generating release notes from GitHub PR references requires three inputs: the new version number, the release date, and the raw changelog data. These inputs enforce formatting and linking rules to properly structure the documentation entries.

Yes, you can use this skill to enforce consistent formatting rules for versioning documentation. It applies strict formatting and linking rules to GitHub release data, ensuring structured release notes with properly categorized highlights and PR links across standard and preview releases.

The best way to structure release management notes for CLI documentation is to categorize highlights and properly link PR references within dedicated markdown files. This approach separates standard and preview releases into appropriate changelog files for consistency.

Manual changelog entries often lack proper PR reference links due to inconsistent formatting. Automating the process with a structured skill enforces linking rules, taking raw GitHub release data and properly formatting categorized highlights with accurate PR references.