Skip to content
TrustedSkillsbeta
Back to all skills

Release Docs

Checked
ratacat·vlatest·writing

Releases documentation updates automatically, streamlining deployments and ensuring developers have accurate, current information for faster workflows.

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 ratacat/claude-skills --skill release-docs -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

ratacat

Taken from the source listing. We haven't verified who controls this account.

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 ratacat/claude-skills at d4b471d05d.

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

Commit
d4b471d05d
Manifest
skills/release-docs/SKILL.md
Scanned
1 file, 204 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

This skill automates the generation of release documentation. It can create comprehensive documents including release notes, upgrade guides, and API change logs based on provided input data like commit messages or issue tracking information. The resulting documentation is formatted for clarity and consistency, ready for distribution to users and developers.

When to use it

  • Automating Release Notes: Generate release notes directly from your Git commit history.
  • Creating Upgrade Guides: Produce detailed upgrade guides based on changes between software versions.
  • Documenting API Changes: Automatically document changes to APIs for developer consumption.
  • Standardizing Documentation: Ensure consistent formatting and structure across all release documentation.

Key capabilities

  • Generates release notes from commit messages.
  • Creates upgrade guides based on version differences.
  • Formats output for readability and consistency.
  • Supports API change log generation.

Example prompts

  • "Generate release notes for version 1.2.0 using the last 10 commits."
  • "Create an upgrade guide from version 1.0 to 1.1, highlighting breaking changes."
  • "Document API changes between versions 2.5 and 2.6 based on these commit messages: [paste commit messages here]."

Tips & gotchas

The quality of the generated documentation heavily relies on clear and descriptive commit messages or issue tracking data. Ensure your development team adheres to consistent commit message conventions for optimal results.