Docs Changelog

This automates changelog updates across three files (latest.md, preview.md, index.md) based on version strings and release notes. It routes stable versus preview releases, handles new minor versions differently from patches, and reformats PR links while stripping contributor sections. The procedural approach is thorough but rigid: it needs exact version formats, assumes specific file structures, and distinguishes between announcement summaries for the main page versus detailed highlights for release pages. Worth using if you maintain multiple changelog files with consistent formatting rules, though you'll need the reference templates it calls out. The preprocessing steps (date conversion, body cleanup) save repetitive manual work.

skills.sh installs: 1.3K
GitHub stars: 108.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add google-gemini/gemini-cli --skill docs-changelog --agent claude-code

Installs into .claude/skills of the current project.

Files

Procedure: Updating Changelog for New Releases

Objective

To standardize the process of updating changelog files (latest.md, preview.md, index.md) based on automated release information.

Inputs

version: The release version string (e.g., v0.28.0, v0.29.0-preview.2).
TIME: The release timestamp (e.g., 2026-02-12T20:33:15Z).
BODY: The raw markdown release notes, containing a "What's Changed" section and a "Full Changelog" link.

Guidelines for `latest.md` and `preview.md` Highlights

Aim for 3-5 key highlight points.
Each highlight point must start with a bold-typed title that summarizes the change (e.g., **New Feature:** A brief description...).
Prioritize summarizing new features over other changes like bug fixes or chores.
Avoid mentioning features that are "experimental" or "in preview" in Stable Releases.
DO NOT include PR numbers, links, or author names in these highlights.
Refer to .gemini/skills/docs-changelog/references/highlights_examples.md for the correct style and tone.