Skip to content
TrustedSkillsbeta
Back to all skills

Docs Changelog

Official
google-gemini·vlatest·writing·Apache-2.0

This skill generates a detailed changelog for documentation updates, streamlining communication and ensuring users are informed of changes.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add google-gemini/gemini-cli --skill docs-changelog -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

google-gemini

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned google-gemini/gemini-cli at fe6350238c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
fe6350238c
Manifest
.gemini/skills/docs-changelog/SKILL.md
Scanned
5 files, 289 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The docs-changelog skill helps users generate and manage changelogs for documentation, making it easier to track updates, improvements, and bug fixes over time. It can automatically parse version history from code repositories or existing documentation files.

When to use it

  • You need to maintain a clear record of changes made to software or documentation.
  • You're preparing a release note for a new version of an application or library.
  • Your team wants to automate the process of updating changelogs during development cycles.

Key capabilities

  • Parses version history from code repositories (e.g., Git logs).
  • Generates structured changelog entries with dates, versions, and descriptions.
  • Supports integration with documentation platforms like GitHub Pages or Read the Docs.

Example prompts

  • "Generate a changelog for the last three releases of our project."
  • "Parse the commit history from the 'develop' branch and format it as a changelog."
  • "Create a markdown changelog file based on the latest version tag."

Tips & gotchas

  • Ensure your repository has proper version tags or commit messages for accurate parsing.
  • This skill works best with projects that follow semantic versioning (SemVer) conventions.