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

by albumentations-team in albumentations-team/AlbumentationsX

Generate release notes for AlbumentationsX. An agent skill from albumentations-team/AlbumentationsX.

AGPL-3.0Auto-check passedDevelopment

Install Release Notes

skills CLI
$ npx skills add albumentations-team/AlbumentationsX --skill release-notes -a claude-code

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

GitHub CLI
$ gh skill install albumentations-team/AlbumentationsX 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/albumentations-team/AlbumentationsX.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/release-notes .claude/skills/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
release-notes
GitHub stars
567
Token cost
~685 tokens
SKILL.md length
320 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Generate release notes for AlbumentationsX. An agent skill from albumentations-team/AlbumentationsX.

  • Works in 6 steps: ## Summary — 3–5 bullet TL;DR. → ## Breaking changes — every… → ## New features — new transforms, new… → …
  • The user asks to prepare
  • SKILL.md covers Where they live, Source of truth for what changed, Required structure and Transform name → link, plus 1 more section
  • Calls git; reaches albumentations.ai

What it does

Release Notes is an agent skill from albumentations-team/AlbumentationsX. Generate release notes for AlbumentationsX. Use when the user asks to prepare, draft, or write release notes for a new version (e.g. "prepare release notes for 2.x.y", "draft release X").

Its SKILL.md is about 690 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: Image augmentation for computer vision. AGPL-3.0-only or commercial licensing. The licence is AGPL-3.0.

When your agent uses it

  • The user asks to prepare
  • Write release notes for a new version (e.g

Example prompts

  • “prepare release notes for 2.x.y”
  • “draft release X”
  • “/release-notes”

Workflow steps

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

  1. ## Summary — 3–5 bullet TL;DR.
  2. ## Breaking changes — every backwards-incompatible change. Be specific (old → new). Include short before/after code snippets when the API…
  3. ## New features — new transforms, new core features, new params on existing transforms.
  4. ## Bug fixes — one entry per fix, link the PR.
  5. ## Misc — CI, build, deps, internal refactors users might notice.
  6. ## Commits — table of commit | PR | description for every commit since the previous tag.

What it can do on your machine

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

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

    • albumentations.ai

    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 loads about 685 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 320 words of instructions outside code blocks.

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

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 albumentations-team/AlbumentationsX at commit 1458043, republished under its AGPL-3.0 licence (© albumentations-team). 320 words, ~685 tokens.

Download SKILL.mdSave it as .claude/skills/release-notes/SKILL.md (or your agent's skills folder).
name
release-notes
description
Generate release notes for AlbumentationsX. Use when the user asks to prepare, draft, or write release notes for a new version (e.g. "prepare release notes for 2.x.y", "draft release X").

Release notes

Where they live

_internal/release_notes/RELEASE_NOTES_<version>.md (e.g. RELEASE_NOTES_2.2.0.md).

Source of truth for what changed

  • git log --oneline <prev_tag>..HEAD and git show --stat <sha> per commit.
  • git diff <prev_tag>..HEAD -- README.md for the canonical added/removed transforms list.
  • git diff <prev_tag>..HEAD -- pyproject.toml for dependency / version bumps.
  • The PR descriptions in commit messages — they're written carefully, mine them for one-liners.

Required structure

  1. ## Summary — 3–5 bullet TL;DR.
  2. ## Breaking changes — every backwards-incompatible change. Be specific (old → new). Include short before/after code snippets when the API surface changed.
  3. ## New features — new transforms, new core features, new params on existing transforms.
  4. ## Bug fixes — one entry per fix, link the PR.
  5. ## Misc — CI, build, deps, internal refactors users might notice.
  6. ## Commits — table of commit | PR | description for every commit since the previous tag.

Match the tone of RELEASE_NOTES_2.1.2.md and RELEASE_NOTES_2.2.0.md: terse, technical, no marketing fluff, no emoji.

Link the first meaningful mention of a transform in each section, including headings and table entries:

markdown
[TransformName](https://albumentations.ai/explore/transform/TransformName/)

Repeated mentions in the same paragraph may use plain backticked names. Keep code fences runnable, without links. For parameter renames, link the transform separately and put the parameter name in code.

Do not link:

  • Core classes (Compose, BboxParams, KeypointParams, BasicTransform, BaseDistortion).
  • Parameter names (angle_range, blur_range).
  • Helper functions (unpack_label_wrappers, to_tuple).
  • Internal modules (core/utils.py).

Other conventions

  • Code references use single backticks for params/files; triple-backtick fenced blocks for code samples.
  • Use the actual commit short SHA (7 chars) and the real PR number in the commits table.
  • "Breaking changes" section comes before "New features" — users scan that first.
  • For mass renames, use a single 2-column table (Old | New) instead of a bullet list.
  • If a feature spans multiple PRs (e.g. instance binding in #222, #223, #237), mention them inline in the prose, not as separate entries.
  • If pyproject.toml version isn't bumped yet, note that in the response to the user; do not bump it as part of writing the notes.

© albumentations-team, AGPL-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 .codex/skills/release-notes of albumentations-team/AlbumentationsX.

Open the folder on GitHubat commit 1458043

Compare with similar skills

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.

Release Notes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Notes this skillalbumentations-team/AlbumentationsX567—~685Automated safety check: PassAGPL-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 yesterday
    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 yesterday
    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 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.

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

More from albumentations-team/AlbumentationsX

All 10 skills in this repo

  • Mixing Transforms

    albumentations-team/AlbumentationsX

    Policy for AlbumentationsX transforms that combine multiple images or objects.

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

  • Performance Optimization

    albumentations-team/AlbumentationsX

    Systematic performance audit for AlbumentationsX runtime code.

    567 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Add Transform

    albumentations-team/AlbumentationsX

    Full checklist for adding a new transform to AlbumentationsX.

    567 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Docstring Deep Dive

    albumentations-team/AlbumentationsX

    Review public AlbumentationsX docstrings for useful descriptions, runnable examples, parameter semantics, and related transforms.

    567 GitHub stars~534 tokensUpdated today
    Auto-check passed

  • License Integrity

    albumentations-team/AlbumentationsX

    Maintain AlbumentationsX license, CLA, provenance notices, and packaged legal artifacts consistently.

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

  • Validate And Fix

    albumentations-team/AlbumentationsX

    After completing code changes, runs tests and pre-commit, then iteratively fixes failures until all pass.

    567 GitHub stars~847 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Release Notes

What does Release Notes do?

Generate release notes for AlbumentationsX. An agent skill from albumentations-team/AlbumentationsX. Release Notes is an agent skill from albumentations-team/AlbumentationsX. Generate release notes for AlbumentationsX.

When should I use Release Notes?

Release Notes fits situations like: the user asks to prepare; write release notes for a new version (e.g.

How do I install Release Notes in Claude Code?

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

How do I install Release Notes in Codex?

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

Can I use 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 albumentations-team/AlbumentationsX --skill 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/release-notes, .gemini/skills/release-notes, .github/skills/release-notes and .opencode/skills/release-notes in your project.

What does Release Notes need to run?

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

Does Release Notes access the network?

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

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

Release Notes is published under the AGPL-3.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 use?

About 685 tokens (SKILL.md is roughly 2.7k 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?

Skills that share tags, products or a category with 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 Release Notes?

albumentations-team (a GitHub organization) maintains it in albumentations-team/AlbumentationsX, which has 567 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.

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