changelog-manager

Generate semantic changelog entries from git diffs and update CHANGELOG.md.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/talhayilmazai/ai-agent-in-customer-repository --skill changelog-manager-talhayilmazai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-manager
Source: https://github.com/talhayilmazai/ai-agent-in-customer-repository/tree/main/.github/skills/changeLog
Command: npx skills add https://github.com/talhayilmazai/ai-agent-in-customer-repository --skill changelog-manager-talhayilmazai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation and maintenance of release notes by analyzing code changes and updating the project's CHANGELOG.md in a consistent, Keep a Changelog-compliant format.

Core Features & Use Cases

  • Changelog generation from diffs: Analyzes git diff or user-provided descriptions to produce clear, categorized entries.
  • Structured entries under Release: Classifies changes into standard types (Added, Changed, Fixed, Removed, etc.) and formats them according to Semantic Versioning.
  • Automated CHANGELOG updates: Inserts new entries under the ## [Released] section, keeping history synchronized with releases.

Quick Start

Use the changelog-manager to generate and apply a release note from the latest git changes.

Frequently Asked Questions about changelog-manager

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

FAQPage Schema
How do I automate changelog generation from git diffs?

Automating changelog generation from git diffs involves analyzing code changes to classify modifications into standard types and updating CHANGELOG.md. This process detects changes, drafts summaries, and formats entries under the [Released] section automatically.

What is the best way to keep a changelog aligned with semantic versioning?

Keeping a changelog aligned with semantic versioning requires structuring release notes into Added, Changed, Fixed, or Removed categories. This approach maintains a standardized history that corresponds directly with semantic versioning release increments.

Can I use manual descriptions instead of git workflows to generate release notes?

You can use manual descriptions to generate release notes. The classification system processes user-provided text, drafts semantic summaries, and inserts them into the CHANGELOG.md file under the [Released] section, exactly as it handles git diff inputs.

Does this approach update existing CHANGELOG.md files or create new ones?

This approach updates existing CHANGELOG.md files by inserting newly generated entries directly under the ## [Released] section. It performs targeted file editing to append categorized changes, keeping your release history synchronized without overwriting previous records.

How are code changes classified when automating semantic changelog updates?

When automating semantic changelog updates, code changes are classified into standard types like Added, Changed, Fixed, and Removed. This categorization ensures entries adhere to Keep a Changelog conventions before being recorded under the [Released] section.