doezer Run
git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-mergesto get commits since the last tag.Determine the new version from the current
release/*branch name (e.g.release/1.3.0→1.3.0).Get today's date in
YYYY-MM-DDformat.Group commits by type using these categories (skip merge commits and anything without meaningful user impact):
- Added —
feat:commits - Fixed —
fix:commits - Changed —
chore:,refactor:,perf:,update:,deps:commits - Security — commits mentioning security, SSRF, CVE, auth, or vulnerability
- Added —
Format the output as a markdown changelog section:
## [VERSION] - DATE ### Added - ... ### Fixed - ... ### Changed - ...Omit sections that have no entries. Write bullet points in plain English (no commit hashes), and mention PR numbers where present.
Read
docs/CHANGELOG.md, then prepend the new section immediately after the# Changelogheader line (before the first existing## [...]section), and write the file back.Display the generated section to the user.
Release Notes by doezer · 770478c
npx skillmds@latest add doezer/release-notes File contents
---name: release-notesdescription: Release Notes---1. Run `git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges` to get commits since the last tag.2. Determine the new version from the current `release/*` branch name (e.g. `release/1.3.0` → `1.3.0`).3. Get today's date in `YYYY-MM-DD` format.4. Group commits by type using these categories (skip merge commits and anything without meaningful user impact): - **Added** — `feat:` commits - **Fixed** — `fix:` commits - **Changed** — `chore:`, `refactor:`, `perf:`, `update:`, `deps:` commits - **Security** — commits mentioning security, SSRF, CVE, auth, or vulnerability5. Format the output as a markdown changelog section: ``` ## [VERSION] - DATE ### Added - ... ### Fixed - ... ### Changed - ... ``` Omit sections that have no entries. Write bullet points in plain English (no commit hashes), and mention PR numbers where present.6. Read `docs/CHANGELOG.md`, then prepend the new section immediately after the `# Changelog` header line (before the first existing `## [...]` section), and write the file back.7. Display the generated section to the user.
doezer/questarr/tree/main/.claude/skills/release-notes-questarr commit 770478cd8a
Frequently asked questions
Run npx skillmds@latest add doezer/release-notes in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Release Notes It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
doezer (@doezer) published this skill. Their other Agent Skills are listed on their SkillMD profile.