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

Release Notes Drafter

by cobusgreyling in cobusgreyling/loop-engineering

Turns a structured list of changes from changelog-scan into a categorized, user-facing release notes draft file, and never publishes anything.

MITAuto-check passedDevelopment

Install Release Notes Drafter

skills CLI
$ npx skills add cobusgreyling/loop-engineering --skill draft-release-notes -a claude-code

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

GitHub CLI
$ gh skill install cobusgreyling/loop-engineering 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/cobusgreyling/loop-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/starters/changelog-drafter/.grok/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
11k
Token cost
~555 tokens
SKILL.md length
234 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Turns a structured list of changes from changelog-scan into a categorized, user-facing release notes draft file, and never publishes anything.

  • Drafting release notes after a changelog scan
  • SKILL.md covers Inputs, Output, Rules and When to Escalate Instead of…
  • Reaches github.com
  • Producing a reviewable RELEASE_NOTES_DRAFT.md for an upcoming release

What it does

The inputs are the structured output of changelog-scan, the previous release version, the target version or an unreleased label, and optional release-voice guidance from AGENTS.md or a project skill. The draft is written to RELEASE_NOTES_DRAFT.md, or printed so the loop can save it, with sections adapted to what exists and empty ones left out. Breaking changes and security items go at the top.

Rules keep items to one line each with a PR link, use the scan's own titles without embellishment, never claim a change that is not in the scanned input, add a one-sentence upgrade note when a step is obvious from the PR, and end with a line asking for human review. The agent escalates instead of drafting when a window holds more than about 40 items, when a breaking or security item needs careful wording, or when the scan says human review is needed first. Afterward the loop records the draft location and a pending review state.

When your agent uses it

  • Drafting release notes after a changelog scan
  • Producing a reviewable RELEASE_NOTES_DRAFT.md for an upcoming release
  • Putting breaking changes and security items at the top of the notes

Example prompts

  • “Draft the release notes for the next version from the changelog scan output.”
  • “Write RELEASE_NOTES_DRAFT.md using our release voice from AGENTS.md.”

Requirements

  • Structured output from the changelog-scan skill

What it can do on your machine

Read from SKILL.md and the folder at commit 87c5e9c. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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

Release Notes Drafter loads about 555 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 234 words of instructions outside code blocks.

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

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 cobusgreyling/loop-engineering at commit 87c5e9c, republished under its MIT licence (© cobusgreyling). 234 words, ~555 tokens.

Download SKILL.mdSave it as .claude/skills/draft-release-notes/SKILL.md (or your agent's skills folder).
name
draft-release-notes
description
Takes a structured list of changes from changelog-scan and produces a clean, categorized, user-facing release notes draft. Follows project voice and conventions. Never publishes — only proposes a draft file or section.
user_invocable
true

Draft Release Notes Skill

Inputs

  • Structured output from changelog-scan (the list of items + summary)
  • Previous release version (from state)
  • Target next version (or "unreleased" / "next")
  • Optional: short "Release voice" guidance from AGENTS.md or a project skill (tone, what to highlight, what to omit)

Output

Write a ready-to-review draft to RELEASE_NOTES_DRAFT.md (or print it clearly so the loop can save it).

Use this structure (adapt section names to what actually exists; omit empty sections):

markdown
# Release Notes — vX.Y.Z (unreleased)

## Breaking Changes
- ...

## Features
- ...

## Bug Fixes
- ...

## Performance
- ...

## Security
- ...

## Documentation & Examples
- ...

## Internal / Maintenance (usually omitted from public notes)
- ...

**Thanks** to @contributor1, @contributor2 for contributions to this release.

**Full changelog**: https://github.com/ORG/REPO/compare/vPREV...HEAD

Rules

  • Be concise and scannable. One line per item when possible, with link to PR.
  • Use the actual title / one-sentence summary from the scan. Do not embellish or add marketing fluff unless the project voice explicitly wants it.
  • Always call out breaking changes and security items at the top.
  • If a change has a user upgrade step that is obvious from the PR, include a one-sentence "Upgrade note".
  • Never claim a change was made if it was not in the scanned input.
  • At the very end of the draft, include a short "Draft generated by loop — please review for accuracy and tone before publishing."

When to Escalate Instead of Drafting

  • More than ~40 items in one window → suggest splitting the release or human curation.
  • Any breaking or security item → include prominent callout and recommend human wordsmithing.
  • The scan summary says "human review needed first".

After writing the draft, the loop should update state with the draft location and "pending human review".

© cobusgreyling, MIT. 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 starters/changelog-drafter/.grok/skills/draft-release-notes of cobusgreyling/loop-engineering.

Open the folder on GitHubat commit 87c5e9c

Compare with similar skills

Release Notes Drafter 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.

Release Notes Drafter compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Notes Drafter this skillcobusgreyling/loop-engineering11k—~555Automated safety check: PassMIT
Simple Englishmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT
StarRocks Release NotesStarRocks/starrocks12k—~1.9kAutomated safety check: NotesApache-2.0
Cutting A ReleaseTriliumNext/Trilium38k—~3.2kAutomated safety check: PassAGPL-3.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Mole CLI Release Flowtw93/Mole70k—~2.5kAutomated safety check: PassGPL-3.0

Similar skills

  • Simple English

    moeru-ai/airi

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

    50k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed

  • StarRocks Release Notes

    StarRocks/starrocks

    Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.

    12k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check: notes

  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed

  • 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 yesterday
    DevelopmentAuto-check passed

  • Mole CLI Release Flow

    tw93/Mole

    Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.

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

  • Release

    PrefectHQ/fastmcp

    Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.

    28k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed

More from cobusgreyling/loop-engineering

All 21 skills in this repo

  • Install Loop Engineering

    cobusgreyling/loop-engineering

    Installs Loop Engineering into a project through the single @cobusgreyling/loop CLI, scaffolding a report-only loop and a readiness score.

    11k GitHub starsUsed in 1 repo~648 tokens
    Auto-check passed

  • Loop Constraints Enforcer

    cobusgreyling/loop-engineering

    Loads a project's loop-constraints.md before any other action and blocks pushes, edits or merges that violate the rules it defines.

    11k GitHub starsUsed in 1 repo~475 tokens
    Auto-check: notes

  • Issue Triage Loop

    cobusgreyling/loop-engineering

    Scans open GitHub issues and discussions, flags duplicates, scores priority and proposes labels into issue-triage-state.md without ever labeling or closing.

    11k GitHub stars~522 tokensUpdated today
    Auto-check passed

  • Loop Triage Report

    cobusgreyling/loop-engineering

    Turns CI failures, open issues, recent commits and chat threads into a prioritized markdown report that an automation loop can act on without inventing architecture work.

    11k GitHub stars~500 tokensUpdated today
    Auto-check passed

  • Loop Token Budget Guard

    cobusgreyling/loop-engineering

    Check token budget and run-log spend before and after a loop run. Enforces early exit when over budget or when there is no actionable work.

    11k GitHub starsUsed in 1 repo~376 tokens
    Auto-check passed

  • PR Review Triage

    cobusgreyling/loop-engineering

    Tracks open pull requests and records CI state, staleness, merge conflicts and unanswered review comments in a state file, then lists the top three actions for a human.

    11k GitHub stars~480 tokensUpdated today
    Auto-check passed

Categories

Questions about Release Notes Drafter

What does Release Notes Drafter do?

Turns a structured list of changes from changelog-scan into a categorized, user-facing release notes draft file, and never publishes anything. md or a project skill.md, or printed so the loop can save it, with sections adapted to what exists and empty ones left out.

When should I use Release Notes Drafter?

Release Notes Drafter fits situations like: drafting release notes after a changelog scan; producing a reviewable RELEASE_NOTES_DRAFT.md for an upcoming release; putting breaking changes and security items at the top of the notes.

How do I install Release Notes Drafter in Claude Code?

Run `npx skills add cobusgreyling/loop-engineering --skill draft-release-notes -a claude-code`. Or copy the skill folder (starters/changelog-drafter/.grok/skills/draft-release-notes in cobusgreyling/loop-engineering) into .claude/skills/draft-release-notes in your project. Claude Code loads it when a task matches its description.

How do I install Release Notes Drafter in Codex?

Run `npx skills add cobusgreyling/loop-engineering --skill draft-release-notes -a codex`. Or copy the skill folder (starters/changelog-drafter/.grok/skills/draft-release-notes in cobusgreyling/loop-engineering) into .agents/skills/draft-release-notes in your project. Codex loads it when a task matches its description.

Can I use Release Notes Drafter 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 cobusgreyling/loop-engineering --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 Release Notes Drafter need to run?

SKILL.md names no scripts, command-line tools or credentials: Release Notes Drafter is instructions for the agent only. Our summary lists: Structured output from the changelog-scan skill.

Does Release Notes Drafter access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Release Notes Drafter 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 Release Notes Drafter use?

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

How many tokens does Release Notes Drafter use?

About 555 tokens (SKILL.md is roughly 2.2k 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 Release Notes Drafter?

Skills that share tags, products or a category with Release Notes Drafter: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and React Router Release Notes Prep (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Notes Drafter?

cobusgreyling (a GitHub user) maintains it in cobusgreyling/loop-engineering, which has 11,440 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

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