aitask-changelog

Generate changelog entries from Git commits and archived task plans.

6|1|Updated Feb 11, 2026

Search Tags:#automation #git #changelog #task management #commits #release notes

Ready to run

npx skills add https://github.com/beyondeye/aitasks --skill aitask-changelog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aitask-changelog
Source: https://github.com/beyondeye/aitasks/tree/main/.claude/skills/aitask-changelog
Command: npx skills add https://github.com/beyondeye/aitasks --skill aitask-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of changelog entries by analyzing Git commits and archived task plans, ensuring your project's release notes are accurate and up-to-date with minimal manual effort.

Core Features & Use Cases

Automated Changelog Generation: Analyzes commits to identify features, bug fixes, and improvements.
Task Integration: Links commits to specific tasks (tNN) and summarizes them using archived plan files.
Version Management: Suggests and validates new version numbers based on semantic versioning.
Overlap Detection: Identifies and helps resolve potential duplicate entries in the changelog.
Use Case: After a development cycle, run this Skill to automatically draft a new section for your CHANGELOG.md, summarizing all completed tasks and their associated commits.

Quick Start

Run the aitask-changelog script to gather release data and begin the changelog generation process.

Frequently Asked Questions about aitask-changelog

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

FAQPage Schema

How do I generate changelog entries from Git commits automatically?▼

To generate changelog entries from Git commits automatically, this Skill analyzes commit messages and archived task plans to identify features, bug fixes, and improvements, summarizing them into release notes with minimal manual effort.

What is the best way to link Git commits to specific tasks for release notes?▼

The best way to link Git commits to specific tasks for release notes is by matching task identifiers like tNN, which allows the Skill to summarize commit details using corresponding archived plan files.

Can I use semantic versioning to manage release numbers in my changelog?▼

Yes, you can manage release numbers in your changelog using semantic versioning, as the Skill suggests and validates new version numbers based on the analyzed commits and task completion data.

How does overlap detection work for duplicate changelog entries?▼

Overlap detection for duplicate changelog entries works by analyzing newly generated summaries against existing entries, identifying potential duplicates to help you resolve overlapping release notes before finalizing the file.

Do I need archived task plans to automate release notes generation?▼

You do not strictly need archived task plans to automate release notes generation, but having them allows the Skill to link commits to specific tasks and provide richer summaries for your changelog entries.