release-notes

SkillDocs & knowledge

Lets your agent turn git commits since the last tag into a formatted changelog section in CHANGELOG.md.

Then ask your AI: use the release-notes skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.

No other account needed.

Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.

About this skill

Generate formatted release notes from git commits since the last tag and prepend them to CHANGELOG.md

What this skill tells your AI

The instructions your AI receives, as published by doezer/questarr in .claude/skills/release-notes-questarr/SKILL.md and read by Ahel’s review.

Run git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges to 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-DD format.
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
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 # Changelog header line (before the first existing ## [...] section), and write the file back.
Display the generated section to the user.

Advanced