Agent Wealth HubFree public resources
中文 EN العربية

Back to catalog / Writing

Gemini CLI changelog: follow the release-version path

Update the latest, preview, or index file from version and raw release data.

Skills

Collect the exact version string, UTC timestamp, and raw release notes first. If the version contains “nightly,” the source workflow stops without changes. Convert the time into ISO and human-readable dates, format PR links in “What’s Changed,” preserve the Full Changelog link, and remove the New Contributors section as directed. For `.0` releases, distinguish stable from preview: stable updates the `index.md` announcement and replaces `latest.md`; preview replaces `preview.md`. Patch releases use their separate path. Produce three to five highlights and omit preview features from stable highlights. This workflow replaces release-note files in the target repository, so verify branch, version, and input before writing.

Permissions

Prerequisites

Permissions

Limitations

Stable, preview, and patch versions follow different paths; dates and release input must be supplied or verified, never invented.

Pinned upstream source

https://github.com/google-gemini/gemini-cli/blob/51617c1bcbcb038291125b092501b4342f4e7f77/.gemini/skills/docs-changelog/SKILL.md

Repository
google-gemini/gemini-cli
File path
.gemini/skills/docs-changelog/SKILL.md
Pinned commit
51617c1bcbcb038291125b092501b4342f4e7f77
Source checked
2026-10-14 · Reviewed against the pinned upstream source

Repository metrics

These values describe the upstream repository, not popularity or likes for an individual skill or playbook.

Stars
Not collected
Forks
Not collected
Observed at
Not collected

No metrics snapshot is available yet.

License: Apache-2.0

Compatible tools

Gemini CLI release notes · Release version and timestamp · Raw changelog body

View skill directory

Main topic

Take a coding Agent change from context to verification

Related resources