acss-kit-changelog-entry

Generate Keep-a-Changelog entries from git history for acss-kit.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/shawn-sandy/agentic-acss-plugins --skill acss-kit-changelog-entry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acss-kit-changelog-entry
Source: https://github.com/shawn-sandy/agentic-acss-plugins/tree/main/.claude/skills/acss-kit-changelog-entry
Command: npx skills add https://github.com/shawn-sandy/agentic-acss-plugins --skill acss-kit-changelog-entry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents slow, inconsistent changelog updates by turning the relevant git history into a correctly categorized Keep-a-Changelog draft.

Core Features & Use Cases

  • Conventional-commit grouping: Converts commit types (feat, fix, docs, refactor, etc.) into the corresponding Keep-a-Changelog sections.
  • Format-preserving output: Matches the existing plugins/acss-kit/CHANGELOG.md structure by following the current “Unreleased” convention.
  • Safe, review-first writing: Produces a proposed entry and requires explicit approval before modifying the changelog.
  • Use case: After tagging and merging multiple changes, generate a ready-to-paste Unreleased summary for acss-kit based on all commits since the last tag.

Quick Start

Tell the AI: Generate a Keep-a-Changelog Unreleased entry for acss-kit from git log since the latest tag, grouped by conventional commit type, and propose the insertion above the latest version in plugins/acss-kit/CHANGELOG.md.

Frequently Asked Questions about acss-kit-changelog-entry

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

FAQPage Schema
How do I generate a changelog entry from git log using conventional commits?

To generate changelog entries, analyze your git log history since the latest tag and map conventional commit types like feat and fix into Keep-a-Changelog sections. This process automatically groups commits into Added, Fixed, and Changed categories for your Unreleased block.

What is the best way to format release notes from git history?

Formatting release notes is best achieved by applying the Keep-a-Changelog standard to your git history. Mapping conventional commit types directly into Added, Fixed, and Changed sections creates a structured Unreleased block ready for review.

Does generating a Keep-a-Changelog entry automatically modify my changelog file?

Generating a Keep-a-Changelog entry does not automatically modify your file. The process proposes an Unreleased block and requires explicit approval before inserting the categorized text above the latest version entry in your changelog.

How do conventional commit types map to Keep-a-Changelog sections?

Conventional commit types map to Keep-a-Changelog sections by converting feat to Added, fix to Fixed, and refactor or docs to Changed. This automatic categorization organizes your git history into a structured release notes format.

Can I use this changelog generation workflow for any git repository?

You cannot use this specific changelog generation workflow for any git repository, as it is configured exclusively for the acss-kit plugin. It targets the plugins/acss-kit/CHANGELOG.md file structure and follows its existing Unreleased convention.