One-click install
npx skills add https://github.com/TriNgo0108/z-command --skill changelog-automation-tringo0108
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/TriNgo0108/z-command/tree/main/templates/skills/changelog-automation
Command: npx skills add https://github.com/TriNgo0108/z-command --skill changelog-automation-tringo0108

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation and maintenance of changelogs, ensuring consistency and saving developers time by adhering to industry standards like Keep a Changelog and Conventional Commits.

Core Features & Use Cases

  • Automated Changelog Generation: Integrates with commit messages to automatically generate release notes.
  • Standardization: Enforces formats like Keep a Changelog and Conventional Commits.
  • Use Case: Streamline your release process by automatically updating your CHANGELOG.md file with each new release, based on your commit history.

Quick Start

Use the changelog-automation skill to generate a changelog from your git commits.

Frequently Asked Questions about changelog-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate changelog generation from git commits?

Automate changelog generation by integrating commit messages with tools like Conventional Changelog or semantic-release to automatically generate release notes. This process parses your git commit history and updates your CHANGELOG.md file automatically with each new release.

What is the Keep a Changelog format and when should I use it for release notes?

The Keep a Changelog format is an industry standard for maintaining a structured record of changes. Use it to standardize release notes generation and ensure consistency across your release workflows when documenting features, fixes, and breaking changes.

Does semantic-release work with Conventional Commits to update CHANGELOG.md?

Yes, semantic-release works with Conventional Commits to automatically update CHANGELOG.md. It parses structured commit messages to determine semantic versioning bumps and generates standardized release notes without manual intervention.

How do I standardize commit conventions for automated release notes?

Standardize commit conventions for automated release notes by adopting Conventional Commits. Tools like commitizen help enforce this format, ensuring your commit history can be reliably parsed to generate structured changelogs and automate semantic versioning.

What's the best way to generate release notes from PRs and releases?

The best way to generate release notes from PRs and releases is using tools like git-cliff or standard-version. They extract data from your pull requests and git tags to populate a Keep a Changelog formatted file automatically during your release workflow.