Skip to content
TrustedSkillsbeta
Back to all skills

Write Release Notes

Official
tldraw·vlatest·writing

Automatically generate clear, concise release notes from commit messages and pull request descriptions.

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 tldraw/tldraw --skill write-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

tldraw

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 tldraw/tldraw at fdd9b4dee0.

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

Commit
fdd9b4dee0
Manifest
skills/write-release-notes/SKILL.md
Scanned
1 file, 126 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

The write-release-notes skill automates the creation of changelogs by analyzing code diffs and commit messages to generate structured release documentation. It transforms raw version control data into human-readable summaries suitable for public distribution or internal team updates.

When to use it

  • Post-deployment: Immediately after merging a feature branch to draft notes for the next release.
  • Release management: Generating standardized changelogs for major version bumps without manual editing.
  • Stakeholder communication: Creating clear summaries of new features, bug fixes, and breaking changes for non-technical audiences.
  • Documentation maintenance: Keeping project READMEs or CHANGELOG.md files up to date automatically.

Key capabilities

  • Parses git diffs and commit logs to identify changes.
  • Categorizes updates into sections like "Added," "Changed," "Deprecated," and "Fixed."
  • Generates markdown-formatted release notes ready for copy-pasting.
  • Supports custom templates or formatting styles based on project needs.

Example prompts

  • "Generate release notes for the latest commit in the main branch, highlighting only breaking changes."
  • "Summarize all bug fixes and new features from the last sprint into a concise changelog entry."
  • "Create formatted release notes for version 2.0 based on these specific commits: [list of hashes]."

Tips & gotchas

Ensure your repository has a clean commit history with descriptive messages, as vague logs may lead to generic output. Review generated notes before publishing to catch context-specific nuances the AI might miss.