skills.rest
cenconq25
cenconq25COMMUNITY
Explore all skills by this author →
GitHub

changelog

Generate structured changelogs from git commits, sprint closures, and PRD updates.

39|6|Updated May 3, 2026
Search Tags:#automation#git#changelog#documentation#prd#sprints#release-notes
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill changelog-cenconq25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill changelog-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates a release window consisting of git commits, sprint closures, and PRD updates into a structured changelog with both internal and user-facing versions.

Core Features & Use Cases

  • Generate an internal engineering changelog with detailed context (features, improvements, fixes, etc.).
  • Produce user-facing release notes suitable for PRD alignment and store requirements.
  • Handle window-based scope with a reproducible process across releases.

Quick Start

Run the changelog workflow for the current release window to generate both internal and user-facing notes.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I auto-generate release notes from git commit history and sprint documentation?▼

You can auto-generate release notes by parsing git commits, sprint closures, and PRD updates to produce a structured changelog with internal engineering context and user-facing summaries.

Can I create both internal engineering changelogs and customer-facing release notes from the same workflow?▼

Yes, the changelog workflow outputs both internal engineering changelogs with detailed context and user-facing release notes suitable for PRD alignment and store requirements.

How do I categorize git commits into features, improvements, fixes, and security updates for a changelog?▼

The changelog process parses commit history and applies optional categorization to group updates into Features, Improvements, Fixes, and Security sections automatically.

What is the best way to maintain a reproducible release notes process across multiple sprint windows?▼

Using a window-based scope ensures a reproducible changelog generation process across releases by consistently integrating git commits, sprint closures, and PRD changes.

Do I need product requirement documents (PRDs) to generate a structured changelog?▼

Including PRD updates is supported but not strictly required; the changelog integrates PRD changes to align user-facing release notes with product requirements and store guidelines.

Does this changelog generation approach work without configuring external dependencies or components?▼

Yes, the changelog workflow operates independently without requiring external dependencies or components, parsing git history and sprint data directly.

Related Skills

Explore More Software Engineering Skills→
scomofoscomofo

changelog

Generate categorized release notes from git history for internal and player audiences.

Community
Advanced
cenconq25cenconq25
39

patch-notes

Generate user-facing patch notes from git history and changelogs.

Community
Intermediate
wanghaishengwanghaisheng
10

changelog

Generates changelogs from git commit history, sprint reports, and design documents.

Community
Advanced
MichaelSolatiMichaelSolati

changelog

Generate categorized internal and player-facing changelogs from git history and sprint reports.

Community
Advanced