New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Draft Release Notes

by luxury-yacht in luxury-yacht/app

Generate release notes from git log since last tag, following [Keep a Changelog](https://keepachangelog.com) and project conventions

GPL-3.0Auto-check passedDevelopment

Install Draft Release Notes

skills CLI
$ npx skills add luxury-yacht/app --skill draft-release-notes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install luxury-yacht/app draft-release-notes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/luxury-yacht/app.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/draft-release-notes .claude/skills/draft-release-notes && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
draft-release-notes
GitHub stars
443
Token cost
~844 tokens
SKILL.md length
405 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
GPL-3.0

At a glance

Generate release notes from git log since last tag, following [Keep a Changelog](https://keepachangelog.com) and project conventions

  • Works in 5 steps: Read the current notes. Compare… → Read commits. Run git log --oneline… → Categorize with Keep a Changelog types,… → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Usage, Steps and Writing Style
  • Calls git

What it does

Draft Release Notes is an agent skill from luxury-yacht/app. Generate release notes from git log since last tag, following [Keep a Changelog](https://keepachangelog.com) and project conventions

Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. It works with Git. The repository describes itself as: Luxury Yacht - A cross-platform app for managing Kubernetes clusters and resources. The licence is GPL-3.0.

When your agent uses it

  • Tasks that involve Changelog and release notes

Example prompts

  • “/draft-release-notes”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Read the current notes. Compare docs/release/pending.md with
  2. Read commits. Run git log --oneline --no-merges, plus
  3. Categorize with Keep a Changelog types, in this order and only when a
  4. Merge each item into its section: fold it into an existing area bullet
  5. Write docs/release/pending.md and show the diff. If the update rewrites

What it can do on your machine

Read from SKILL.md and the folder at commit 09c8d2d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Draft Release Notes loads about 844 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 405 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~844

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from luxury-yacht/app at commit 09c8d2d, republished under its GPL-3.0 licence (© luxury-yacht). 405 words, ~844 tokens.

Download SKILL.mdSave it as .claude/skills/draft-release-notes/SKILL.md (or your agent's skills folder).
name
draft-release-notes
description
Generate release notes from git log since last tag, following [Keep a Changelog](https://keepachangelog.com) and project conventions

Release Notes

Draft the unreleased notes in docs/release/pending.md from commits since the last tag. cmd/project/release.go inserts that file verbatim below the ## Release / ## Beta Release heading and version lines from docs/release/template.md, so the file holds only category sections and bullets: no version, date, or release heading.

Usage

/draft-release-notes [<from-tag> [<to-ref>]] — the range defaults to the latest tag (git tag --sort=-v:refname | head -1) through HEAD.

Steps

  1. Read the current notes. Compare docs/release/pending.md with git show <from-tag>:docs/release/pending.md. Identical content is the already-tagged release: start a fresh file. Otherwise the entries are unreleased: keep their wording and merge into them.
  2. Read commits. Run git log <range> --oneline --no-merges, plus git log <range> --oneline --merges for PR merge commits (they carry the PR title and number). For unclear messages, run git show <sha> --stat and read key files to understand the user-visible effect.
  3. Categorize with Keep a Changelog types, in this order and only when a category has entries: Added (new features, UI elements, capabilities), Changed (existing functionality, UX, behavior), Deprecated (marked for future removal), Removed (deleted features), Fixed (bugs, stability), Security (vulnerabilities, auth).
  4. Merge each item into its section: fold it into an existing area bullet as a sub-bullet, or tighten that bullet, before adding a new one. Never duplicate an entry already present.
  5. Write docs/release/pending.md and show the diff. If the update rewrites or removes existing unreleased entries rather than only adding, show the proposed file and wait for approval before writing.
markdown
### Added

- Area or feature with a short summary
  - Notable detail
  - Notable detail

### Changed

- Short description of the change

### Fixed

- Short description of the fix
Show full SKILL.md (161 more words)Show less

Writing Style

  • Write for users skimming what changed. "Favorites save views with their filters", not "implement fav persistence layer with JSON serialization."
  • Lead with the feature or area name. "Rollback for Deployments, DaemonSets, and StatefulSets", not "Added a new modal that lets you roll back."
  • Group by area. A plain lead bullet names the area; two-space-indented sub-bullets give specifics. Keep each bullet to one short sentence; no paragraph-length entries.
  • Group related fixes from one effort under one bullet ("Pod logs viewer is more reliable").
  • Section headings are ### Markdown headings (### Added); do not bold category or area names.
  • Leave out PR numbers and commit hashes, version bumps, merge commits, CI/build-only and internal changes without a user-visible effect, cosmetic details (spacing, icon sizes), and fixes to features that are new in these same unreleased notes.
  • Deprecated, Removed, and Security appear only with entries, but never omit them when they have entries: deprecations, removals, and breaking changes are the most important things to document.

© luxury-yacht, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/draft-release-notes of luxury-yacht/app.

Open the folder on GitHubat commit 09c8d2d

Compare with similar skills

Draft Release Notes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Draft Release Notes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Draft Release Notes this skillluxury-yacht/app443—~844Automated safety check: PassGPL-3.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
Mole Release Notes Publishertw93/Mole70k—~1.9kAutomated safety check: PassGPL-3.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Mole Release Notes Publisher

    tw93/Mole

    Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

More from luxury-yacht/app

All 17 skills in this repo

  • Improve Backend

    luxury-yacht/app

    A skill your agent uses when wanting to systematically improve the Go backend - scans for security vulnerabilities, stability risks, performance issues, and code simplification opportunities, then…

    443 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Improve Frontend

    luxury-yacht/app

    A skill your agent uses when wanting to systematically improve the React/TypeScript frontend - scans for security vulnerabilities, stability risks, performance issues, and code simplification…

    443 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Make Impossible States Impossible

    luxury-yacht/app

    Eliminate representable-but-invalid Luxury Yacht states with discriminated unions, required identity, typed status, validated constructors, or one boundary chokepoint; use for "make impossible…

    443 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Add Resource

    luxury-yacht/app

    Add or extend support for a Kubernetes resource kind across the required catalog, refresh, detail, object-panel, object-map, permission, documentation, and test surfaces

    443 GitHub stars~704 tokensUpdated today
    Auto-check passed

  • App Review

    luxury-yacht/app

    Audit broad Luxury Yacht systems or cross-cutting concerns for structural simplification, hardening, optimization, or refactoring; use for app-wide reviews and phased structural plans, not branch…

    443 GitHub stars~818 tokensUpdated today
    Auto-check passed

  • Browse Tables

    luxury-yacht/app

    Change cluster or namespace views, Browse/catalog surfaces, shared GridTable behavior, filters, pagination, large datasets, metrics columns, or refresh-backed resource tables

    443 GitHub stars~518 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Draft Release Notes

What does Draft Release Notes do?

Generate release notes from git log since last tag, following [Keep a Changelog](https://keepachangelog.com) and project conventions. Draft Release Notes is an agent skill from luxury-yacht/app.

When should I use Draft Release Notes?

Draft Release Notes fits situations like: tasks that involve Changelog and release notes.

How do I install Draft Release Notes in Claude Code?

Run `npx skills add luxury-yacht/app --skill draft-release-notes -a claude-code`. Or copy the skill folder (.agents/skills/draft-release-notes in luxury-yacht/app) into .claude/skills/draft-release-notes in your project. Claude Code loads it when a task matches its description.

How do I install Draft Release Notes in Codex?

Run `npx skills add luxury-yacht/app --skill draft-release-notes -a codex`. Or copy the skill folder (.agents/skills/draft-release-notes in luxury-yacht/app) into .agents/skills/draft-release-notes in your project. Codex loads it when a task matches its description.

Can I use Draft Release Notes in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add luxury-yacht/app --skill draft-release-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/draft-release-notes, .gemini/skills/draft-release-notes, .github/skills/draft-release-notes and .opencode/skills/draft-release-notes in your project.

What does Draft Release Notes need to run?

Going by SKILL.md and its folder, Draft Release Notes needs the command-line tools its instructions call (git).

Does Draft Release Notes access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Draft Release Notes safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Draft Release Notes use?

Draft Release Notes is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Draft Release Notes use?

About 844 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Draft Release Notes?

Skills that share tags, products or a category with Draft Release Notes: React Router Release Notes Prep (remix-run/react-router, 57k stars), Draft Release Notes (jamiepine/voicebox, 57k stars), Mole Release Notes Publisher (tw93/Mole, 70k stars) and Release Bump (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Draft Release Notes?

luxury-yacht (a GitHub organization) maintains it in luxury-yacht/app, which has 443 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 8, 2026.

Source: luxury-yacht/app on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.