From atum-workflows
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.
npx claudepluginhub arnwaldn/atum-plugins-collection --plugin atum-workflowsThis skill uses the workspace's default tool permissions.
- Branch: !`git branch --show-current`
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
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).