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.
Installs into .claude/skills of the current project.
Are you the author of Changelog Automation?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/rootcastleco-changelog-automation)
---
name: changelog-automation
description: "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."
risk: unknown
source: rootcastle-rei
---
# 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.
---
> 🏰 **Rei Skills** — Curated by [Rootcastle Engineering & Innovation](https://www.rootcastle.com) | Batuhan Ayrıbaş
> Engineering Beyond Boundaries | admin@rootcastle.com
