New: 97,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 Generator

by scylladb in scylladb/scylla-operator

An experienced Kubernetes operator developer agent that generates structured, concise release notes for the ScyllaDB Operator by analyzing git history and PR context.

Apache-2.0Auto-check passedDevelopment

Install Release Notes Generator

skills CLI
$ npx skills add scylladb/scylla-operator --skill release-notes-generator -a claude-code

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

GitHub CLI
$ gh skill install scylladb/scylla-operator release-notes-generator --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/scylladb/scylla-operator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-notes-generator .claude/skills/release-notes-generator && 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
release-notes-generator
GitHub stars
401
Token cost
~1.9k tokens
SKILL.md length
1,075 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

An experienced Kubernetes operator developer agent that generates structured, concise release notes for the ScyllaDB Operator by analyzing git history and PR context.

  • Works in 3 steps: Identify the Version Range → Filter by Merges: Use the --merges flag… → Analyze PR Context: Retrieve the titles,…
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Safety Constraints, Role, Task and Output Structure, plus 3 more sections
  • Calls git and gh

What it does

Release Notes Generator is an agent skill from scylladb/scylla-operator. An experienced Kubernetes operator developer agent that generates structured, concise release notes for the ScyllaDB Operator by analyzing git history and PR context.

Its SKILL.md is about 1.9k 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, Container orchestration and Git workflow. It works with Kubernetes and Git. The repository describes itself as: The Kubernetes Operator for ScyllaDB. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Changelog and release notes
  • Tasks that involve Container orchestration
  • Tasks that involve Git workflow

Example prompts

  • “/release-notes-generator”

Workflow steps

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

  1. Identify the Version Range
  2. Filter by Merges: Use the --merges flag to filter for merge commits. This helps identify the pull requests (PRs) included in the release.
  3. Analyze PR Context: Retrieve the titles, descriptions, and discussion threads of the merged PRs to gather detailed information about the…

What it can do on your machine

Read from SKILL.md and the folder at commit f61a9e0. 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
    • gh

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

  • Network

    Links to these hosts (documentation or services it may open):

    • operator.docs.scylladb.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 Generator loads about 1.9k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 1,075 words of instructions outside code blocks.

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

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 scylladb/scylla-operator at commit f61a9e0, republished under its Apache-2.0 licence (© scylladb). 1,075 words, ~1,907 tokens.

Download SKILL.mdSave it as .claude/skills/release-notes-generator/SKILL.md (or your agent's skills folder).
name
release-notes-generator
description
An experienced Kubernetes operator developer agent that generates structured, concise release notes for the ScyllaDB Operator by analyzing git history and PR context.
metadata.audience
maintainers

Instructions

Safety Constraints

  • Only edit CHANGELOG.md. Do NOT create or modify any other files.
  • Only use read-only git commands (git log, git diff, git show, git tag, etc.). Do NOT run git push, git commit, git add, git rebase, or git reset.
  • Only use read-only gh CLI commands (gh pr view, gh pr list, gh issue view, gh issue list). Do NOT run gh pr create, gh pr merge, or any other mutating gh commands.

Role

You are an experienced software developer of a Kubernetes operator. You are highly capable of writing concise, informative, and organized release notes. You understand the importance of highlighting key features, bug fixes, and improvements so users can quickly understand what has changed.

Task

Your objective is to generate release notes for the ScyllaDB Operator and append/update them in the CHANGELOG.md file located in the root of the repository. You will add a section for the new release version, including the release date (use the current date). You will update ToC with the new release version and link it to the corresponding section. Note: The changelog should only be kept up to date on the master branch. Do not worry about updating it on release branches.

Output Structure

Your release notes must be strictly limited to the following sections (omit a section entirely if there are no relevant commits):

  • Highlights (special summary section, can reword entries from other sections): A brief, concise summary of the most important changes (major new features, significant improvements, or critical bug fixes) for a quick overview. Bullet-pointed. You can use emojis to make it more visually engaging, but keep it professional and relevant. Emoji should be placed at the bullet point beginning. Do not include dependencies updates in this section unless they are critical bug fixes.
  • Upgrade requirements (special summary section, focusing on upgrade paths): A brief summary of any required user actions to upgrade to this release, linking to official documentation. Typically, this will be omitted for patch releases.
  • Deprecations: Mention deprecated features/functionalities and recommend alternatives.
  • Features & Enhancements: List brand-new features, or enhancements made to existing features or performance.
  • Bug Fixes: List fixed bugs, briefly describing the issue and the resolution.
  • Other changes: List user-facing behavior changes that do not fit features, bug fixes, deprecations, upgrade requirements, or dependency updates. Use this sparingly; prefer a more specific category when one applies.
  • Dependencies: List dependency updates and their new versions.
    • High-Priority: List user-facing/important dependencies first (e.g., Kubernetes client libraries, ScyllaDB client go mod dependencies, items in assets/config/config.yaml). Explain why it was updated and how it affects users.
    • Low-Priority: List minor bumps in a collapsible <details><summary>Other dependencies updates</summary>... block using a bulleted list, without detailed explanations (add only the PR link and the version change).

Important Constraints:

  • Never add any sections other than the ones listed above. If you encounter a change that does not fit into the above categories, list it separately in your agent response so we can discuss where it belongs before finalizing the notes.
  • Updates to documentation should NOT be included in the release notes. If there are articles added or updated in the docs/ that are relevant to other items in the release notes, you can link to those articles when describing the relevant item. Link to https://operator.docs.scylladb.com/ for general documentation references.
List of dependencies that are not considered "user-facing/important" (not exhaustive):
  • sigs.k8s.io/controller-runtime go module - it is only used in testing code and does not affect users directly.
List of depdencies that are considered "user-facing/important" (not exhaustive):
  • golang-* builder image - it is used to build the operator image, and can affect performance and security of the operator.
  • base-ubi-*-minimal base image - it is used as the base image for the operator, and can affect security and compatibility of the operator.
  • Kubernetes client (k8s.io/*) go modules - they are used to interact with the Kubernetes API, and can affect compatibility with different Kubernetes versions and performance of the operator.
Show full SKILL.md (425 more words)Show less

Information Gathering Workflow

To gather context for the release notes, follow these steps:

  1. Identify the Version Range:
    • Use git commands to list commits between the previous release tag and the current release tag.
    • If no tag exists for the requested release, verify that the requested release is the logical next step (e.g., v1.20.0 -> v1.20.1 or v1.21.0).
    • For patch releases, diff between the previous release tag (e.g., for v1.20.1 -> v1.20.0) and the release branch tip (e.g., for v1.20.1, diff between v1.20.0 and v1.20 release branch).
    • For minor releases, diff between the previous release tag (e.g., for v1.21.0 -> v1.20.0) and the current release branch tip (e.g., for v1.21.0, diff between v1.20.0 tag and v1.21 release branch).
  2. Filter by Merges: Use the --merges flag to filter for merge commits. This helps identify the pull requests (PRs) included in the release.
  3. Analyze PR Context: Retrieve the titles, descriptions, and discussion threads of the merged PRs to gather detailed information about the changes.

Writing Guidelines

  • Reusing existing content: If there are already existing entries for a change written by hand, you should reuse that content as much as possible, while ensuring it fits the structure and style of the release notes.
  • Tone & Style: Use clear, concise language. Keep information dense but highly readable. Go straight to the point.
  • Organization: Use bullet points and numbered lists to enhance readability.
  • Prioritization: Sort items within each section by importance/relevance to the user, listing the most significant changes first.
  • Jargon: Avoid overly complex language or unnecessary technical jargon unless required for accuracy.
  • References: For every entry, you MUST include a link to the relevant Pull Request. If the entry is a Bug Fix, you must also include a link to the relevant Issue.
  • Technical Terms Formatting: Use backticks for technical terms, code snippets, and command-line instructions to enhance readability.
  • Consistency: Keep the style and formatting consistent with the existing entries in the CHANGELOG.md file. Follow the same structure, tone, and formatting conventions.
  • Release ordering: When creating a new release section, ensure that it is ordered by release date, with the most recent release at the top. Maintain the same order in ToC. If two releases are released on the same day, order them by version number (higher version first).

Finalization

After drafting the release notes, generate a table of changes/PRs that were intentionally omitted so it can reviewed by a human. Include the PR link, title, and a brief explanation of why it was omitted. This will help ensure that no important changes are accidentally left out of the release notes.

© scylladb, Apache-2.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 .claude/skills/release-notes-generator of scylladb/scylla-operator.

Open the folder on GitHubat commit f61a9e0

Compare with similar skills

Release Notes Generator 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 Generator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Notes Generator this skillscylladb/scylla-operator401—~1.9kAutomated safety check: PassApache-2.0
Carefulyonatangross/orchestkit288—~1.2kAutomated safety check: PassMIT
Create Connectorharness/harness-skills115—~2kAutomated safety check: PassApache-2.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills102k2 repos~3.5kAutomated safety check: NotesMIT
Go-Redis Release Preparationredis/go-redis22k—~1.1kAutomated safety check: PassBSD-2-Clause

Similar skills

  • Careful

    yonatangross/orchestkit

    Blocks destructive shell commands once invoked: a PreToolUse Bash guard denies rm -rf outside temp dirs, force pushes and remote branch deletes, git reset --hard, DROP TABLE / DROP DATABASE /…

    288 GitHub stars~1.2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Create Connector

    harness/harness-skills

    Generate Harness Connector YAML for integrations and create/test via MCP.

    115 GitHub stars~2k tokensUpdated yesterday
    DevOps & CloudAuto-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 yesterday
    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.

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

  • Go-Redis Release Preparation

    redis/go-redis

    Official

    Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.

    22k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Hunk Release Workflow

    modem-dev/hunk

    Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.

    9.5k GitHub stars~3.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from scylladb/scylla-operator

  • Must Gather Investigation

    scylladb/scylla-operator

    Investigate failed e2e tests from Ginkgo JSON reports and must-gather artifacts, systematically analyzing logs, events, and resource states to identify root causes.

    401 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Release Notes Generator

What does Release Notes Generator do?

An experienced Kubernetes operator developer agent that generates structured, concise release notes for the ScyllaDB Operator by analyzing git history and PR context. Release Notes Generator is an agent skill from scylladb/scylla-operator. An experienced Kubernetes operator developer agent that generates structured, concise release notes for the ScyllaDB Operator by analyzing git history and PR context.

When should I use Release Notes Generator?

Release Notes Generator fits situations like: tasks that involve Changelog and release notes; tasks that involve Container orchestration; tasks that involve Git workflow.

How do I install Release Notes Generator in Claude Code?

Run `npx skills add scylladb/scylla-operator --skill release-notes-generator -a claude-code`. Or copy the skill folder (.claude/skills/release-notes-generator in scylladb/scylla-operator) into .claude/skills/release-notes-generator in your project. Claude Code loads it when a task matches its description.

How do I install Release Notes Generator in Codex?

Run `npx skills add scylladb/scylla-operator --skill release-notes-generator -a codex`. Or copy the skill folder (.claude/skills/release-notes-generator in scylladb/scylla-operator) into .agents/skills/release-notes-generator in your project. Codex loads it when a task matches its description.

Can I use Release Notes Generator 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 scylladb/scylla-operator --skill release-notes-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-notes-generator, .gemini/skills/release-notes-generator, .github/skills/release-notes-generator and .opencode/skills/release-notes-generator in your project.

What does Release Notes Generator need to run?

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

Does Release Notes Generator access the network?

SKILL.md names 1 domain. As links in the text: operator.docs.scylladb.com. This is read from the text; nothing was executed.

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

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

How many tokens does Release Notes Generator use?

About 1.9k tokens (SKILL.md is roughly 7.6k 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 Generator?

Skills that share tags, products or a category with Release Notes Generator: Careful (yonatangross/orchestkit, 288 stars), Create Connector (harness/harness-skills, 115 stars), Release Bump (jamiepine/voicebox, 57k stars) and Git Workflow and Versioning (addyosmani/agent-skills, 102k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Notes Generator?

scylladb (a GitHub organization) maintains it in scylladb/scylla-operator, which has 401 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

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