Skip to content
TrustedSkillsbeta
Back to all skills

Update Release Notes

Official
tldraw·vlatest·writing

Automatically generates updated release notes from your project’s commit history, streamlining documentation and improving transparency for users.

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 update-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.

Scanned
6 files, 644 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 allows AI agents to automatically generate and update release notes for software projects. It streamlines the documentation process by extracting relevant changes directly from code commits or pull requests into a structured, human-readable format.

When to use it

  • Automating changelog generation after a series of feature branches are merged.
  • Ensuring consistent formatting across multiple open-source repositories.
  • Providing immediate visibility into new features for users without manual intervention.
  • Reducing the administrative burden on developers who must manually write release notes.

Key capabilities

  • Parses commit messages and pull request descriptions to identify changes.
  • Categorizes updates into sections like "Added," "Changed," or "Fixed."
  • Generates Markdown-formatted release notes ready for deployment.
  • Integrates seamlessly with existing CI/CD pipelines via tldraw infrastructure.

Example prompts

  • "Generate a release note summary for the latest merge to the main branch."
  • "Update the CHANGELOG.md file based on recent pull requests in this repository."
  • "Create a formatted list of new features added in the last sprint using commit data."

Tips & gotchas

Ensure your commit messages follow a consistent convention (e.g., Conventional Commits) for accurate parsing. This skill relies on tldraw-specific integrations, so it may not function outside that ecosystem without additional configuration.