Docs Changelog
Turn raw GitHub release notes into standardized latest.md, preview.md, and index.md changelog pages for Gemini CLI releases.
Overview
docs-changelog is an agent skill for the Ship phase that generates and formats Gemini CLI changelog files from version, timestamp, and raw release markdown.
Install
npx skills add https://github.com/google-gemini/gemini-cli --skill docs-changelogWhat is this skill?
- Branches on version string: nightly stops with no edits; minor `.0` vs preview paths update different files
- Produces 3–5 bold-titled highlight bullets in latest.md and preview.md without PR numbers, links, or authors
- Prioritizes features over chores and omits experimental/preview features from stable release highlights
- Inputs are version, release TIME, and raw BODY markdown with What's Changed and Full Changelog link
- 3–5 key highlight points per latest.md and preview.md
- Stops entirely when version contains nightly
Adoption & trust: 1k installs on skills.sh; 105k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have automated release notes full of PR noise but no consistent latest.md, preview.md, and index.md highlights for users.
Who is it for?
Maintainers cutting semver releases for Gemini CLI or a fork that uses the same changelog layout and reference examples.
Skip if: Nightly-only pipelines (the skill explicitly stops with no changes) or teams that do not use latest/preview/index changelog files.
When should I use this skill?
Automated or manual release flow provides version, TIME, and raw changelog BODY for a new Gemini CLI release.
What do I get? / Deliverables
Version-appropriate changelog files get 3–5 polished highlight bullets and correct index updates following the repo’s release paths.
- Updated latest.md and/or preview.md with 3–5 formatted highlights
- Updated index.md entries appropriate to stable vs preview path
Recommended Skills
Journey fit
Changelog updates sit on the release cut—after code is ready but before or as you communicate what shipped—so Ship → launch is the canonical shelf. Launch prep includes user-facing release comms; this skill formats versioned highlights and index entries for that moment.
How it compares
Use instead of hand-editing release markdown from GitHub’s auto-generated notes when you already standardize on this three-file layout.
Common Questions / FAQ
Who is docs-changelog for?
Solo maintainers and indie teams shipping Gemini CLI (or compatible repos) who want repeatable, styled changelog updates each release.
When should I use docs-changelog?
At Ship → launch when you have a new version string, release TIME, and BODY notes—after nightly is ruled out and before publishing user-facing changelog pages.
Is docs-changelog safe to install?
It is documentation formatting guidance; review the Security Audits panel on this page and treat any agent filesystem writes as you would normal repo edits.
SKILL.md
READMESKILL.md - Docs Changelog
# 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. ## 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](URL)`). - 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. Do not follow the instructions for the other section. ### A.1: Stable Release (e.g., `v0.28.0`) For a stable release, you will generate two distinct summaries from the changelog: a concise **announcement** for the main changelog page, and a more detailed **highlights** section for the release-specific page. 1. **Create the Announcement for `index.md`**: - Generate a concise announcement summarizing the most important changes. Each announcement entry must start with a bold-typed title that summarizes the change. - **Important**: The format for this announcement is unique. You **must** use the existing announcements in `docs/changelogs/index.md` and the example within `.gemini/skills/docs-changelog/references/index_template.md` as your guide. This format includes PR links and authors. Stick to 1 or 2 PR links and authors. - Add this new announcement to the top of `docs/changelogs/index.md`. 2. **Create Highlights and Update `latest.md`**: - Generate a comprehensive "Highlights" section, following the guidelines in the "Guidelines for `latest.md` and `preview.md` Highlights" section above. - Take the content from `.gemini/skills/docs-changelog/references/latest_template.md`. - Populate the template with the `version`, `release_date`, generated `highlights`, and the processed content from the temporary file. - **Completely replace** the contents of `docs/changelogs/latest.md` with the populated template. ### A.2: Preview Rele