skills.rest
sdcorejs
sdcorejsCOMMUNITY
Explore all skills by this author →
GitHub

sdcorejs-changelog

Generate Keep a Changelog entries from Conventional Commits history.

2|Updated Apr 18, 2026
Search Tags:#automation#changelog#conventional commits#release notes#semver#git history#keep a changelog
One-click install
npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdcorejs-changelog
Source: https://github.com/sdcorejs/sdcorejs-agent/tree/main/plugin/skills/sdcorejs-changelog
Command: npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill sdcorejs-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of scanning git history and rewriting release notes by turning Conventional Commits into a clean, user-facing CHANGELOG entry.

Core Features & Use Cases

  • Conventional Commit classification: Groups commits into audience-meaningful sections (Added/Changed/Fixed/etc.) and flags BREAKING changes.
  • Semver bump suggestion: Determines whether the release should be major, minor, patch, or no-release based on commit types.
  • Keep a Changelog formatting: Inserts an entry under the correct ## [Unreleased] / version block and uses consistent language (VI/EN) with existing entries.
  • Release and release-note workflows: Works for manual “what changed since vX.Y.Z” requests and auto-invocation during sdcorejs-ship release mode.

Quick Start

Ask the agent to write a changelog for your next release by specifying the baseline tag (or let it use the last tag found).

Frequently Asked Questions about sdcorejs-changelog

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

FAQPage Schema
How do I generate a changelog from conventional commits automatically?▼

Generating a Keep a Changelog entry from conventional commits involves grouping commit history into audience-meaningful sections, flagging BREAKING changes, and suggesting a major, minor, or patch semver bump.

How does semver bump suggestion work from git history?▼

Semver bump suggestion works by analyzing conventional commit types in your git history to determine whether the release should be major, minor, patch, or no-release, based on the presence of breaking changes or feature additions.

Can I use this to generate release notes for a Next.js or NestJS repository?▼

This works for Next.js, NestJS, and Angular Portal repositories by reading their conventional commit history and producing a Keep a Changelog formatted entry with appropriate semver bump suggestions.

What is the best way to maintain a Keep a Changelog file from conventional commits?▼

The best way to maintain a Keep a Changelog file is to automate entry insertion by reading git history since the last tag, classifying conventional commits into sections, and preserving any existing user edits.

How do I prevent a changelog generator from overwriting my manual edits?▼

This Skill prevents overwriting manual edits by inserting new changelog entries under the correct Unreleased or version block while preserving existing user edits in the file.

Does the changelog generator support Vietnamese language release notes?▼

Yes, the changelog generator supports Vietnamese language release notes by analyzing existing Keep a Changelog entries and using consistent VI or EN language for the newly inserted conventional commit classifications.

Related Skills

Explore More Content & Communication Skills→
gaebalaigaebalai
2

release-tag-plan

Plan release tagging and CHANGELOG strategy using semantic versioning.

Community
Advanced
rodacatorodacato

ship

Bump project versions, finalize CHANGELOGs, and create GitHub releases.

Community
Advanced
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
nmdranmdra
26

keep-a-changelog

Parse Git commit history and format CHANGELOG.md entries per Keep a Changelog standards.

Community
Intermediate