changelog

Analyze Git commit history and summarize changes into structured JSON changelog files.

Updated Dec 30, 2025
One-click install
npx skills add https://github.com/kshehadeh/prompt --skill changelog-kshehadeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/kshehadeh/prompt/tree/main/.agents/skills/changelog
Command: npx skills add https://github.com/kshehadeh/prompt --skill changelog-kshehadeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of documenting recent code changes into a structured JSON format, suitable for generating notifications about software updates.

Core Features & Use Cases

  • Automated Change Logging: Analyzes commit history to identify and summarize discrete changes.
  • Structured Output: Formats changes into a JSON object with details like commit hash, type, area, and impact.
  • Duplicate Prevention: Avoids adding redundant entries for the same commit or change.
  • Use Case: After deploying a new feature, this Skill can automatically generate a changelog entry that can be used to inform users about the update.

Quick Start

Use the changelog skill to document changes from the last 7 days.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate a changelog from git commit history?

To generate a changelog from git commit history, this skill analyzes recent commits and summarizes them into a structured JSON format. It categorizes discrete changes by type, area, and impact level to document updates for notifications.

How can I automate code change documentation for deployment notifications?

Automating code change documentation involves parsing git commits and structuring them into JSON objects with details like commit hash and impact. This skill prevents duplicate entries to ensure accurate daily changelog records for deployment notifications.

What is the best way to structure git commits into JSON for release notes?

Structuring git commits into JSON for release notes requires extracting details like commit hash, type, and impact. This skill categorizes changes across areas like content, profile, and tools, formatting them accurately into daily changelog files.

How do I prevent duplicate entries when generating a changelog from git commits?

Preventing duplicate entries when generating a changelog from git commits requires checking existing records against new changes. This skill identifies discrete changes and avoids adding redundant entries for the same commit to maintain accurate logs.

Can I categorize git commits by impact level for automated changelogs?

Yes, you can categorize git commits by impact level for automated changelogs. This skill identifies changes and categorizes them by impact, such as patch, minor, or major, alongside type and area, outputting structured JSON.