mcpbeat

Changelog Automation

dokhacgiakhoa/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.

4k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill changelog-automation

What comes with it

13 324 bytes besides the instruction
sub-skills/implementation-playbook.md

The instruction itself

8 sections, as written by the author

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.

🧠 Knowledge Modules (Fractal Skills)

1. implementation-playbook

How to use it

Copy the folder

Take dokhacgiakhoa/changelog-automation from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.