multiAI Summary Pending
changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
231 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/changelog-automation/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/sickn33/changelog-automation/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/changelog-automation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How changelog-automation Compares
| Feature / Agent | changelog-automation | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Changelog Automation Patterns and tools for automating changelog generation, release notes, and version management following industry standards. ## Use this skill when - Setting up automated changelog generation - Implementing conventional commits - Creating release note workflows - Standardizing commit message formats - Managing semantic versioning ## Do not use this skill when - The project has no release process or versioning - You only need a one-time manual release note - Commit history is unavailable or unreliable ## Instructions - Select a changelog format and versioning strategy. - Enforce commit conventions or labeling rules. - Configure tooling to generate and publish notes. - Review output for accuracy, completeness, and wording. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Safety - Avoid exposing secrets or internal-only details in release notes. ## Resources - `resources/implementation-playbook.md` for detailed patterns, templates, and examples.