changelog

Generate Keep a Changelog entries from Git commit diffs.

2|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/Integralist/agent-skills --skill changelog-integralist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/Integralist/agent-skills/tree/main/.agents/skills/changelog
Command: npx skills add https://github.com/Integralist/agent-skills --skill changelog-integralist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

Manually updating the project's CHANGELOG.md file is time-consuming and prone to errors. This Skill automates the process by generating new entries based on the latest commits.

Core Features & Use Cases

  • Commit Analysis: Automatically identifies changes from uncommitted diffs or branch vs. main comparisons.
  • Entry Generation: Creates Keep a Changelog 1.1.0 compliant entries.
  • Use Case: When you need to update your project's CHANGELOG.md file with new entries based on recent changes.

Quick Start

Use the changelog skill to add a new entry to the CHANGELOG.md based on the current branch.

Frequently Asked Questions about changelog

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

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

You can automatically generate a changelog from git commits by analyzing commit diffs and applying Keep a Changelog guidelines to update your project's CHANGELOG.md file with new entries.

How does analyzing uncommitted changes work for changelog generation?

Analyzing uncommitted changes works by reading your current working directory diffs to identify modifications, which are then formatted into Keep a Changelog compliant entries for your CHANGELOG.md file.

Can I generate changelog entries by comparing my current branch to the main branch?

Yes, you can generate changelog entries by comparing your current branch to the main branch, allowing you to capture all specific differences and update your project's CHANGELOG.md file accordingly.

What is the best way to format a CHANGELOG.md file according to Keep a Changelog standards?

The best way to format a CHANGELOG.md file is to apply Keep a Changelog 1.1.0 guidelines, automatically categorizing commit analysis results into standardized entry types for consistent project documentation.

Does this changelog automation require Git to be installed in my environment?

Yes, this changelog automation requires Git to be installed in your environment, as it relies on Git commands to analyze uncommitted diffs and branch comparisons to generate the entries.

What are the limitations of automating changelog updates from commit history?

A limitation of automating changelog updates from commit history is that entry quality depends entirely on the descriptiveness of your original commit messages and the accuracy of the analyzed Git diffs.