patch-notes

Generate categorized patch notes from git history and changelogs.

70|42|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/tranhieutt/software_development_department --skill patch-notes-tranhieutt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: patch-notes
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/patch-notes
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill patch-notes-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill translates dense development logs, sprint retrospectives, balance tweaks, and QA bug records into polished, user-friendly patch notes so players understand what changed without developer jargon.

Core Features & Use Cases

  • Cross-source synthesis: Reads changelog files, git history, sprint reflections, balance documents, and QA data to build a comprehensive picture of release changes.
  • Categorized storytelling: Groups updates into new content, business logic, quality of life, bug fixes, performance, and known issues while keeping descriptions focused on user experience.
  • Flexible presentation: Outputs brief, detailed, or full styles with optional developer commentary and saves the curated notes to the production release directory for version tracking.

Quick Start

Ask for patch notes for version 1.2.0 in detailed style so the skill compiles history, categorizations, and balance numbers into a user-ready summary.

Frequently Asked Questions about patch-notes

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

FAQPage Schema
How do I generate user-facing patch notes from git history and changelogs?▼

Generate user-facing patch notes by synthesizing git history, sprint retrospectives, and QA bug logs into categorized summaries. The skill translates dense developer records into polished descriptions grouped by new content, bug fixes, and performance so players understand changes without jargon.

Can I create categorized release notes from QA bug logs and sprint retrospectives?▼

Yes, you can create categorized release notes from QA bug logs and sprint retrospectives. The skill reads these sources alongside balance documents to group updates into distinct categories like quality of life, business logic, and known issues while focusing descriptions on user experience.

What is the best way to format game balance changes for player communication?▼

The best way to format game balance changes is to categorize them under business logic and new content within your patch notes. This skill compiles balance numbers and changelog documents into a user-ready summary, removing developer jargon to keep players informed.

How do I save compiled patch notes to a specific production release directory?▼

You save compiled patch notes by directing the skill to output the curated markdown file to the production/releases/[version]/patch-notes.md path. This ensures your generated release notes are properly versioned and tracked within your production environment.

Does the patch notes generation support different output styles and detail levels?▼

Yes, patch notes generation supports brief, detailed, and full output styles. You can request a specific style like detailed to compile history, categorizations, and balance numbers into a user-ready summary with optional developer commentary for added context.