Generates and formats changelog files for new releases with version-aware templates and highlight extraction.
Works with
Handles three release types: stable minor versions, stable patches, and preview releases, each with distinct file update procedures
Automatically processes raw markdown release notes by reformatting PR URLs to markdown links and removing contributor sections
Generates concise 3–5 point highlight summaries for release announcements, prioritizing new features over bug fixes
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondocs-changelogExecute the skills CLI command in your project's root directory to begin installation:
Fetches docs-changelog from google-gemini/gemini-cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate docs-changelog. Access via /docs-changelog in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
100.4K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
100.4K
stars
To standardize the process of updating changelog files (latest.md,
preview.md, index.md) based on automated release information.
v0.28.0,
v0.29.0-preview.2).2026-02-12T20:33:15Z).latest.md and preview.md Highlights**New Feature:** A brief description...)..gemini/skills/docs-changelog/references/highlights_examples.md
for the correct style and tone.version
string.
version contains "nightly", STOP. No changes are made.version ends in .0, follow the Path A: New Minor Version
procedure.version does not end in .0, follow the Path B: Patch Version
procedure.TIME input into two formats for later use:
yyyy-mm-dd and Month dd, yyyy.BODY content to a temporary file for processing.[#12345](URL)).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.
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:
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.docs/changelogs/index.md.Create Highlights and Update latest.md:
latest.md and preview.md Highlights" section
above..gemini/skills/docs-changelog/references/latest_template.md.version, release_date, generated
highlights, and the processed content from the temporary file.docs/changelogs/latest.md with
the populated template.v0.29.0-preview.0)preview.md:
.gemini/skills/docs-changelog/references/preview_template.md.version, release_date, generated
highlights, and the processed content from the temporary file.docs/changelogs/preview.md
with the populated template.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.
v0.28.1)docs/changelogs/latest.mdUpdate 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. Change
Full Changelog: https://github.com/google-gemini/gemini-cli/compare/v0.28.2…v0.29.0
to
Full Changelog: https://github.com/google-gemini/gemini-cli/compare/v0.28.2…v0.29.1
v0.29.0-preview.3)docs/changelogs/preview.mdUpdate 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. Change
Full Changelog: https://github.com/google-gemini/gemini-cli/compare/v0.28.2…v0.29.0-preview.0
to
Full Changelog: https://github.com/google-gemini/gemini-cli/compare/v0.28.2…v0.29.0-preview.1
npm run format ONLY to ensure consistency.Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
google-gemini/gemini-cli
langchain-ai/deepagents
upstash/context7
zrong/skills
lombiq/tailwind-agent-skills
patricio0312rev/skills
Useful defaults in docs-changelog — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: docs-changelog is the kind of skill you can hand to a new teammate without a long onboarding doc.
docs-changelog is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
docs-changelog reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for docs-changelog matched our evaluation — installs cleanly and behaves as described in the markdown.
We added docs-changelog from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: docs-changelog is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend docs-changelog for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added docs-changelog from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
docs-changelog reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 73