Skip to content
TrustedSkillsbeta
Back to all skills

Writing Release Notes

Checked
danbars·vlatest·writing

Automatically generates clear, concise release notes from commit messages and issue tracking data.

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 danbars/skills --skill writing-release-notes -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

danbars

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 danbars/skills at eadcbf784d.

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

Commit
eadcbf784d
Manifest
assistant-b/skills/writing-release-notes/SKILL.md
Scanned
1 file, 45 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 generates release notes based on provided information about software changes. It can synthesize details from commit messages, issue tracker entries, or feature descriptions to produce a formatted and informative document suitable for public consumption. The output is designed to clearly communicate what's new in a release to users.

When to use it

  • Automating Release Note Creation: Quickly generate draft release notes for a new software version.
  • Summarizing Feature Changes: Condense detailed feature descriptions into concise and user-friendly summaries.
  • Translating Technical Jargon: Convert technical commit messages into language understandable by non-technical users.
  • Generating Release Notes from Issue Tracker Data: Automatically create release notes based on closed issues in a project's issue tracker.

Key capabilities

  • Generates formatted release note documents.
  • Synthesizes information from various sources (commit messages, feature descriptions).
  • Converts technical language to user-friendly explanations.

Example prompts

  • "Write release notes for version 2.5 based on these commit messages: [list of commit messages]"
  • "Summarize the changes in this feature description into a release note entry: [feature description text]"
  • “Create release notes from these closed issues: [issue tracker data]”

Tips & gotchas

The quality of the generated release notes depends heavily on the clarity and detail of the input provided. Ensure commit messages are descriptive and feature descriptions are well-written for optimal results.