docs-changelog
Provides a step-by-step procedure for generating Gemini CLI changelog files based on github release information.
Install
mkdir -p .claude/skills/docs-changelog && curl -L -o skill.zip "https://mcp.directory/api/skills/download/1450" && unzip -o skill.zip -d .claude/skills/docs-changelog && rm skill.zipInstalls to .claude/skills/docs-changelog
About this skill
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.mdfor the correct style and tone.
Initial Processing
- Analyze Version: Determine the release path based on the
versionstring.- If
versioncontains "nightly", STOP. No changes are made. - If
versionends in.0, follow the Path A: New Minor Version procedure. - If
versiondoes not end in.0, follow the Path B: Patch Version procedure.
- If
- Process Time: Convert the
TIMEinput into two formats for later use:yyyy-mm-ddandMonth dd, yyyy. - Process Body:
- Save the incoming
BODYcontent 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.
- Save the incoming
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.
-
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.mdand the example within.gemini/skills/docs-changelog/references/index_template.mdas 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.
-
Create Highlights and Update
latest.md:- Generate a comprehensive "Highlights" section, following the guidelines
in the "Guidelines for
latest.mdandpreview.mdHighlights" section above. - Take the content from
.gemini/skills/docs-changelog/references/latest_template.md. - Populate the template with the
version,release_date, generatedhighlights, and the processed content from the temporary file. - Completely replace the contents of
docs/changelogs/latest.mdwith the populated template.
- Generate a comprehensive "Highlights" section, following the guidelines
in the "Guidelines for
A.2: Preview Release (e.g., v0.29.0-preview.0)
- Update
preview.md:- Generate a comprehensive "Highlights" section, following the highlight guidelines.
- Take the content from
.gemini/skills/docs-changelog/references/preview_template.md. - Populate the template with the
version,release_date, generatedhighlights, and the processed content from the temporary file. - Completely replace the contents of
docs/changelogs/preview.mdwith the populated template.
Path B: Patch Version
Use this path if the version number does not end in .0.
Important: Based on the version, you must choose to follow either section B.1 for stable patches or B.2 for preview patches. Do not follow the instructions for the other section.
B.1: Stable Patch (e.g., v0.28.1)
- Target File:
docs/changelogs/latest.md - Perform the following edits on the target file:
-
Update the version in the main header. The line should read,
# Latest stable release: {{version}} -
Update the rease date. The line should read,
Released: {{release_date_month_dd_yyyy}} -
Determine if a "What's Changed" section exists in the temporary file If so, continue to step 4. Otherwise, skip to step 5.
-
Prepend the processed "What's Changed" list from the temporary file to the existing "What's Changed" list in
latest.md. Do not change or replace the existing list, only add to the beginning of it. -
In the "Full Changelog", edit only the end of the URL. Identify the last part of the URL that looks like
...{previous_version}and update it to be...{version}.Example: assume the patch version is
v0.29.1. ChangeFull Changelog: https://github.com/google-gemini/gemini-cli/compare/v0.28.2…v0.29.0toFull Changelog: https://github.com/google-gemini/gemini-cli/compare/v0.28.2…v0.29.1
-
B.2: Preview Patch (e.g., v0.29.0-preview.3)
- Target File:
docs/changelogs/preview.md - Perform the following edits on the target file:
-
Update the version in the main header. The line should read,
# Preview release: {{version}} -
Update the rease date. The line should read,
Released: {{release_date_month_dd_yyyy}} -
Determine if a "What's Changed" section exists in the temporary file If so, continue to step 4. Otherwise, skip to step 5.
-
Prepend the processed "What's Changed" list from the temporary file to the existing "What's Changed" list in
preview.md. Do not change or replace the existing list, only add to the beginning of it. -
In the "Full Changelog", edit only the end of the URL. Identify the last part of the URL that looks like
...{previous_version}and update it to be...{version}.Example: assume the patch version is
v0.29.0-preview.1. ChangeFull Changelog: https://github.com/google-gemini/gemini-cli/compare/v0.28.2…v0.29.0-preview.0toFull Changelog: https://github.com/google-gemini/gemini-cli/compare/v0.28.2…v0.29.0-preview.1
-
Finalize
- After making changes, run
npm run formatONLY to ensure consistency. - Delete any temporary files created during the process.
More by google-gemini
View all →You might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
rust-coding-skill
UtakataKyosui
Guides Claude in writing idiomatic, efficient, well-structured Rust code using proper data modeling, traits, impl organization, macros, and build-speed best practices.
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.