Agent skill · writing content · google-gemini
docs-changelog
Generates and formats changelog files for a new release based on provided version and raw changelog data.
Why this skill is useful
Adds a structured automation process for generating changelog files that standardizes release documentation.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 106,400 stars on the source repository.
What this skill does
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/highlightsexamples.md for the correct style and tone. Initial Processing 1. Analyze Version: Determine the release path based on the version string. If version contains "nightly", STOP. No changes are made. If version ends in .0, follow the Path A: New Minor Version procedure. If version does not end in .0, follow the Path B: Patch Version procedure. 2. Process Time: Convert the TIME input into two formats for later use: yyyy-mm-dd and Month dd, yyyy. 3. Process Body: Save the incoming BODY content to a temporary file for processing. In the "What's Changed" section of the temporary file, reformat all pull request URLs to be markdown links with the PR number as the text (e.g., #12345). If a "New Contributors" section exists, delete it. Preserve the "Full Changelog" link. The processed content of this temporary file will be used in subsequent steps. --- Path A: New Minor Version Use this path if the version number ends in .0. Important: Based on the version, you must choose to follow either section A.1 for stable releases or A.2 for preview releases. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google-gemini/docs-changelog