skills.rest
echoVic
echoVicCOMMUNITY
Explore all skills by this author →
Website𝕏@echo_vicGitHub

devops/changelog-generation

Generates CHANGELOG entries from git commit history and pipeline artifacts following Conventional Commits.

553|50|Updated Jan 10, 2026
Search Tags:#release notes#Conventional Commits#Automation#Versioning#Git history#ChangeLog#devOps
One-click install
npx skills add https://github.com/echoVic/boss-skill --skill devops-changelog-generation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devops/changelog-generation
Source: https://github.com/echoVic/boss-skill/tree/main/skill/skills/devops/changelog-generation
Command: npx skills add https://github.com/echoVic/boss-skill --skill devops-changelog-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually writing release changelogs after a deployment is tedious and error-prone, often resulting in missing changes or inconsistent formatting. This Skill automates CHANGELOG generation by parsing git history and pipeline artifacts into a standardized, user-facing release record.

Core Features & Use Cases

  • Git History Parsing: Extracts commits since the last tag and classifies them by Conventional Commits types (feat, fix, perf, refactor, docs) into Keep a Changelog categories.
  • Pipeline Artifact Integration: Enriches entries with user-facing descriptions from PRD, deploy report, and task list files under .boss/<feature>/.
  • Dual Output Modes: Writes .boss/<feature>/changelog.md and optionally prepends the new version section to an existing root CHANGELOG.md.
  • Use Case: After a successful deployment of a new feature, automatically produce a versioned changelog with breaking changes flagged, commit hash references, and merged scope entries.

Quick Start

Generate a changelog for the current release based on commits since the last git tag and the pipeline artifacts in .boss.

Frequently Asked Questions about devops/changelog-generation

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

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

Parse commits since the last git tag using git log, classify them by Conventional Commits prefixes like feat and fix, then format them into Keep a Changelog sections. This Skill automates that flow and writes the result to a changelog file.

What commit format is needed for automatic changelog generation?▼

Conventional Commits format (type(scope): description) works best, mapping feat to Added, fix to Fixed, and perf to Performance. Non-conventional commits are classified by keyword inference, and unclassifiable ones fall under Changed.

Does changelog generation work without git tags?▼

Yes. If no tag exists, it falls back to the most recent 50 commits. For versioning, it uses package.json version first, then the latest git tag, and finally a date-based format like YYYY.MM.DD.

How are breaking changes handled in generated changelogs?▼

Commits marked as BREAKING CHANGE are always placed at the top of the release section under a warning-flagged heading. This ensures consumers of the changelog see incompatible changes before anything else.

Can it update an existing CHANGELOG.md file?▼

Yes. If a root CHANGELOG.md exists, the new version section is inserted before the first existing version entry. If none exists, a new file is created with the standard Keep a Changelog header.

Related Skills

Explore More Software Engineering Skills→
wise-clawwise-claw
10

trellis-finish-work

Verify task completion, archive Trellis tasks, and record session progress.

Official
Intermediate
Roeia1Roeia1
13

publish

Automate SAGA releases by bumping versions, updating changelogs, and publishing artifacts.

Community
Advanced
jim60105jim60105
21

bump-version

Automate semantic version bumps, changelog generation, and Git tagging.

Community
Advanced
Sir-chawakornSir-chawakorn
33

changelog-generator

Generate changelogs from Git commits in Markdown format.

Community
Intermediate