changelog

Name: changelog
Availability: InStock
Author: Instrument

Generate markdown change logs from git history between tagged versions.

3|Updated Apr 6, 2026

Search Tags:#git #release management #version control #change log #software release

Ready to run

npx skills add https://github.com/instrument-org/instrument --skill changelog-instrument-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/instrument-org/instrument/tree/main/.agents/skills/changelog
Command: npx skills add https://github.com/instrument-org/instrument --skill changelog-instrument-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Manually creating detailed change logs for software releases is time-consuming and error-prone. This Skill automates the process of generating change logs from git history, reducing human effort and improving accuracy.

Core Features & Use Cases

Automated Version Comparison: Compares the most recent tagged version with the previous one.
Commit Analysis: Inspects larger commits to include relevant changes.
Markdown Formatting: Outputs the change log in a user-friendly markdown format.
Use Case: When releasing a new version of a software product, this Skill can quickly generate a comprehensive change log, detailing new features, bug fixes, and other significant updates.

Quick Start

Generate the change log for the most recent non-beta release of the project using the changelog skill.

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 change log from git history for a new software release?▼

To generate a change log from git history, you can automate the process by comparing the most recent tagged version with the previous one. This Skill inspects relevant commits to extract and format new features and bug fixes into markdown.

What is the best way to format git commit messages into a markdown change log?▼

Formatting a markdown change log from git commits is best handled by automated version comparison. This process extracts new features and bug fixes from your git history since the last release and outputs them in a user-friendly markdown format.

How does automated version comparison work for extracting software release notes?▼

Automated version comparison for release notes works by evaluating your git history to identify the most recent tagged version and the one preceding it. It then analyzes larger commits within that range to include relevant software changes.

Do I need specific version control practices to generate a change log from git?▼

Generating a change log from git requires the git environment and knowledge of common version control practices. Your project must utilize tagged releases so the tool can accurately compare versions and extract the correct commit history.

Can this automated change log generator analyze larger commits for significant updates?▼

Yes, an automated change log generator can analyze larger commits. It inspects these substantial commits within your git history to ensure relevant changes, such as significant updates and bug fixes, are included in the final markdown output.

Why should I use an automated change log generator instead of manually tracking software releases?▼

You should use an automated change log generator because manually creating detailed logs for software releases is time-consuming and error-prone. Automating this extraction from git history reduces human effort and significantly improves accuracy.