changelog-generator

Generate CHANGELOG.md from conventional commits with semver-based versioning.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Vivekmano27/agent-orchestrator --skill changelog-generator-vivekmano27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/Vivekmano27/agent-orchestrator/tree/main/plugins/project-orchestrator/skills/changelog-generator
Command: npx skills add https://github.com/Vivekmano27/agent-orchestrator --skill changelog-generator-vivekmano27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing release notes can be tedious and error-prone; this skill automates changelog creation by parsing git history using the conventional commit format and organizing entries into standard categories.

Core Features & Use Cases

  • Parses conventional commits to categorize changes (Added, Changed, Fixed, Security) and supports per-scope grouping for monorepos.
  • Generates a Keep a Changelog style CHANGELOG.md and helps determine the next version based on commit history.
  • Supports release preparation, tagging workflows, and producing a reproducible narrative of what changed.

Quick Start

Run the generator on your repository to produce a complete CHANGELOG.md.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I auto-generate release notes from conventional commits?

To auto-generate release notes, you can parse conventional commits to group changes into Added, Changed, Fixed, and Security categories. This process creates a structured, Keep a Changelog style CHANGELOG.md file from your git history.

Can I generate per-scope changelogs for a monorepo?

Yes, you can generate per-scope changelogs for monorepos. The generator supports grouping changes by scope, ensuring each package receives its own categorized release notes based on its specific conventional commit history.

How does conventional commit parsing determine the next semver version?

Semver-based bump decisions are determined by parsing commit history for specific conventional commit types. Breaking changes trigger a major bump, new features a minor bump, and fixes a patch bump for your release.

What is the best way to maintain a Keep a Changelog style CHANGELOG.md?

The best way to maintain a Keep a Changelog style CHANGELOG.md is to automate generation by extracting commits since the last tag. This ensures standards-compliant output by automatically grouping entries into Added, Changed, Fixed, and Security sections.

Does the changelog generator work without external dependencies?

Yes, the changelog generator works without external dependencies. It handles commit-extraction, semver-based bump decisions, and automated output natively to produce your CHANGELOG.md file.