Changelog

Name: Changelog
Availability: InStock
Author: @aaronjmars

Analyze recent GitHub commits and generate categorized Markdown changelogs.

17|1|Updated Mar 25, 2026

Search Tags:#automation #git #changelog #project management #commit #reporting

Ready to run

npx skills add https://github.com/aaronjmars/miroshark-aeon --skill changelog-aaronjmars

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Changelog
Source: https://github.com/aaronjmars/miroshark-aeon/tree/main/skills/changelog
Command: npx skills add https://github.com/aaronjmars/miroshark-aeon --skill changelog-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of detailed changelogs by analyzing recent commits across watched repositories, helping teams maintain transparent project histories without manual effort.

Core Features & Use Cases

Commit Aggregation: Retrieves recent commit data from multiple GitHub repositories.
Categorization: Groups commits into features, fixes, docs, chores, and others based on conventional commit prefixes.
Changelog Report: Produces a well-structured Markdown changelog summarizing recent development activities.
Use Case: A development team wants weekly updates on their project updates to share with stakeholders easily, automatically generating reports from their commit histories.

Quick Start

Input your list of watched repositories and run the skill to automatically generate and save a weekly changelog with commit summaries.

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 GitHub commit history?▼

To automatically generate a changelog from GitHub commit history, this skill retrieves recent commits across watched repositories and compiles them into a structured Markdown report. It analyzes commit data using conventional prefixes to categorize development activities.

How does automatic commit categorization work for project changelogs?▼

Automatic commit categorization for project changelogs works by parsing conventional commit prefixes like feature, fix, docs, and chore. This skill aggregates recent GitHub commits and groups them accordingly to produce an organized Markdown summary.

Can I aggregate commits from multiple GitHub repositories into one report?▼

Yes, you can aggregate commits from multiple GitHub repositories into one report. By inputting your list of watched repositories, this skill retrieves recent commit data from each and compiles a comprehensive weekly changelog summarizing all development activities.

What is the best way to track weekly development progress for stakeholders?▼

The best way to track weekly development progress for stakeholders is to automatically generate a changelog from your commit history. This skill provides a well-structured Markdown report summarizing recent features and fixes, ensuring project transparency without manual effort.

Do I need git APIs to generate a Markdown changelog automatically?▼

Yes, you need git APIs to generate a Markdown changelog automatically. This skill requires git APIs to retrieve recent commit data from watched GitHub repositories and Markdown processing capabilities to format the final project documentation.