mcpField
C
changelog-automation

changelog-automation

github.com/sickn33Development49.2k220 installsUpdated 1d ago
Repository

About changelog-automation

A skill for teams setting up automated changelogs, release notes, and version management. It covers commit conventions, release workflows, and review of generated notes.

Key features

  1. 01Changelog format and version strategy
  2. 02Commit conventions and labeling
  3. 03Automated release note generation
  4. 04Review for accuracy and completeness
  5. 05Guidance on release-note safety

Use cases

  1. 01Set up automated changelog generation
  2. 02Standardize commit message formats
  3. 03Create release note workflows
  4. 04Manage semantic versioning

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill changelog-automation

After installing, type/changelog-automationin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

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.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported