changelog-generator

Generate markdown release notes from Conventional Commits and lint commit messages.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/LuminairPrime/openwrt-docs4ai-pipeline --skill changelog-generator-luminairprime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/LuminairPrime/openwrt-docs4ai-pipeline/tree/main/.agents/skills/changelog-generator
Command: npx skills add https://github.com/LuminairPrime/openwrt-docs4ai-pipeline --skill changelog-generator-luminairprime

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Manually drafting release notes from commit histories is error‑prone and time‑consuming; this Skill automates the creation of consistent, auditable changelogs directly from Conventional Commits.

Core Features & Use Cases

  • Parse commits using Conventional Commit rules and infer the semantic version bump.
  • Render Keep a Changelog sections in markdown or JSON for inclusion in release documentation.
  • Lint commit messages to enforce format before merges, enabling CI integration.
  • Generate entries from git ranges, stdin, or file inputs, supporting monorepo scoped changelogs.
  • Integrate with CI pipelines to automatically produce draft notes on tag pushes.

Quick Start

Request the changelog‑generator skill to produce a markdown release note for commits between v1.2.0 and v1.3.0.

Frequently Asked Questions about changelog-generator

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

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

You can generate release notes from conventional commits by running a Python script that parses your git history, applies conventional commit rules, infers the semantic version bump, and renders Keep a Changelog markdown sections.

What is the best way to automate changelog creation in a CI pipeline?

Automating changelog creation in a CI pipeline involves integrating Python parsing scripts that trigger on tag pushes, lint commit messages before merges, and output draft release notes directly from your git ranges.

Does this changelog generator support monorepo scoped release notes?

Yes, monorepo scoped release notes are supported; the generator parses commit messages from specific git ranges, stdin, or file inputs to produce scoped changelog entries for individual packages.

Can I lint git commit messages to enforce conventional commits format before merging?

Yes, you can lint git commit messages to enforce the conventional commits format before merges, enabling CI integration and ensuring your commit history remains structured for automated semantic versioning.

Do I need Python 3 to run the changelog generation scripts?

Yes, a Python 3 environment is required to run the parsing, bump determination, and markdown rendering scripts that generate your changelog and release notes from git commit history.