changelog

Summarize git history and sprint reports into structured changelog markdown.

70|42|Updated Mar 27, 2026

Search Tags:#changelog #sprint-planning #release-notes #git-history #design-docs #product-communication

Ready to run

npx skills add https://github.com/tranhieutt/software_development_department --skill changelog-tranhieutt

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of tracking commits, sprint reports, and design docs across releases so you can publish consistent internal and external changelogs quickly.

Core Features & Use Cases

Dual-output changelog generation: Produces both detailed internal logs and concise user-facing summaries for any version tag or sprint.
Context-aware categorization: Reads commit history, sprint reports, and design documents to classify changes into features, improvements, bug fixes, balance shifts, and known issues.
Release preparation use case: Use it after a sprint to aggregate technical details for engineering leadership while simultaneously crafting user-friendly updates for stakeholders.

Quick Start

Ask the changelog skill to summarize the release notes for version 3.1 using recent commits and sprint context.

Frequently Asked Questions about changelog

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

FAQPage Schema

How do I generate release notes from git history and sprint reports?▼

To generate release notes from git history, you aggregate commit logs, sprint context, and design docs to classify changes into structured categories like features, improvements, and bug fixes. This produces dual markdown outputs for both internal tracking and user-facing summaries.

What is the best way to summarize commits for internal and user-facing changelogs?▼

Summarizing commits for changelogs involves reading git history alongside sprint reports and design documents to categorize changes by impact. It yields detailed engineering logs for leadership and concise summaries for external stakeholders.

Can I use git history and design docs to categorize bug fixes and features for a sprint?▼

Yes, you can use git history and design docs to categorize sprint deliverables by analyzing commit messages and design context. It automatically classifies changes into features, improvements, bug fixes, balance shifts, and known issues for release preparation.

Do I need git access and sprint reports to prepare changelog narratives for a version tag?▼

Yes, preparing changelog narratives for a specific version tag requires git availability and access to production sprint reports, design document archives, and changelog templates to accurately categorize changes and generate markdown output.

How does categorizing design documents and commit logs improve release preparation workflows?▼

Categorizing design documents and commit logs improves release preparation by removing manual tracking effort across systems. It aggregates technical details and sprint context to publish consistent internal and external changelogs quickly for any specified sprint number.

Are there limitations when generating changelogs without changelog templates or design document archives?▼

Generating changelogs without design document archives or templates limits the ability to deeply categorize changes and structure narratives. The process relies on these inputs alongside git history and sprint reports to produce accurate internal and user-facing markdown outputs.