release-notes · justxor — Claude Code skill: what it does, how to install
Generates release notes and CHANGELOG entries between Git tags or from the latest tag to HEAD using Conventional Commits.
MIT ★ 353 updated 2026-10-01
npx skills add justxor/claude-code-pro-course --skill release-notes -a claude-codeWhat release-notes does
This skill extracts commit history with git log excluding merge commits across a given range. When you omit tag arguments, it determines the starting tag automatically via git describe --tags --abbrev=0 and targets HEAD.
Entries are classified by Conventional Commits types. Breaking changes are placed at the very top, followed by features, fixes, and performance updates. Secondary tasks such as chore, docs, and ci get condensed into a single line. The skill translates raw commit messages into user-facing product updates.
Whenever CHANGELOG.md exists in the project, the skill offers to prepend the new section following Keep a Changelog conventions. Repositories without tags require passing explicit commit bounds directly.
What it helps with
- generate release notes between two Git tags
- translate technical commit messages into user updates
- isolate breaking changes into an upfront warning section
- prepend a release block into an existing CHANGELOG.md
Example prompts for the agent
- Draft release notes from the latest tag
- Generate a changelog between tags v1.2.0 and v1.3.0
- Review unreleased commits and update CHANGELOG.md
How to install release-notes
1Skills CLI (Vercel)
npx skills add justxor/claude-code-pro-course --skill release-notes -a claude-code2Manually: put the files in place
~/.claude/skills/release-notes/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/release-notes/
1Skills CLI (Vercel)
npx skills add justxor/claude-code-pro-course --skill release-notes -a codex2Manually: put the files in place
.agents/skills/release-notes/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add justxor/claude-code-pro-course --skill release-notes -a cursor2Manually: put the files in place
.cursor/skills/release-notes/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install justxor/claude-code-pro-course starter-kit/.claude/skills/release-notes2Manually: put the files in place
.github/skills/release-notes/SKILL.md1Skills CLI (Vercel)
npx skills add justxor/claude-code-pro-course --skill release-notes -a gemini-cli2Platform CLI
gemini skills install https://github.com/justxor/claude-code-pro-course --path starter-kit/.claude/skills/release-notesManually: put the files in place
.devin/skills/release-notes/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about release-notes
How to install release-notes in Claude Code?
Run npx skills add justxor/claude-code-pro-course --skill release-notes -a claude-code or save the skill file directly to ~/.claude/skills/release-notes/SKILL.md.
What does the release-notes skill do?
It parses commit history via Git, sorts items by Conventional Commits conventions, and crafts readable changelogs for end users.
Which tools does the skill require?
It needs Bash execution permissions for git log, git tag, and git describe, along with file Read and Edit access.
Source text
SKILL.md · MIT
--- name: release-notes description: Генерирует release notes / CHANGELOG между двумя тегами или от последнего тега. Используй, когда просят release notes, changelog или список изменений релиза. allowed-tools: Bash(git log:*), Bash(git tag:*), Bash(git describe:*), Read, Edit argument-hint: "[от-тега] [до-тега]" --- # Release notes Диапазон: `$ARGUMENTS` (если пусто — от последнего тега `git describe --tags --abbrev=0` до HEAD). 1. `git log <от>..<до> --pretty=format:'%h %s (%an)' --no-merges` 2. Сгруппируй по типам Conventional Commits: - ✨ Новое (`feat`) - 🐛 Исправления (`fix`) - ⚡ Производительность (`perf`) - ♻️ Рефакторинг и прочее (`refactor`, `chore`, `docs`, `ci`) — кратко, одной строкой - 💥 **Breaking changes** (`!` или `BREAKING CHANGE`) — всегда первым блоком 3. Переписывай технические сообщения на язык пользователя: что изменилось для него. 4. Если есть `CHANGELOG.md` — предложи добавить секцию сверху (формат Keep a Changelog).
© justxor · MIT · justxor/claude-code-pro-course
Similar skills
All skills for Git and GitHub →release-notes by other authors comes first.