Generate release notes from git commits since the last tag or a given ref. Use when the user asks to generate release notes, changelog, or summarize recent changes for a release.
From atum-systemnpx claudepluginhub arnwaldn/atum-system --plugin atum-systemThis skill uses the workspace's default tool permissions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Integrates PayPal payments with express checkout, subscriptions, refunds, and IPN. Includes JS SDK for frontend buttons and Python REST API for backend capture.
git branch --show-currentgit describe --tags --abbrev=0 2>/dev/null || echo "no tags yet"git log $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~20)..HEAD --oneline 2>/dev/null || git log --oneline -20Generate release notes from the git history above.
Group commits by conventional commit type:
Rewrite each commit as a user-friendly one-liner (not the raw commit message)
Highlight breaking changes with a dedicated section if any commit contains BREAKING CHANGE or !:
Format as markdown with the version/date as heading:
## [version or "Unreleased"] - YYYY-MM-DD
### New Features
- Description of feature
### Bug Fixes
- Description of fix
If $ARGUMENTS is provided, use it as the version name. Otherwise use "Unreleased".
Output in the language matching the project (French if README/docs are in French, English otherwise).
CHANGELOG.md auto-update — If a CHANGELOG.md file exists at the project root:
# Changelog heading)CHANGELOG.md exists, offer to create one with the current release as first entryIf $ARGUMENTS contains --changelog, ONLY update CHANGELOG.md (skip console output).