docs-changelog
Generates and formats changelog files for a new release based on provided version and raw changelog data.
Install
With your agent
Install OMGSkills skill "google-gemini/gemini-cli:docs-changelog" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/google-gemini/gemini-cli /tmp/gemini-cli && ln -s /tmp/gemini-cli/.gemini/skills/docs-changelog ~/.claude/skills/docs-changelogFrom README
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.