patch-notes

Generate categorized release notes from changelogs and git history.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill patch-notes-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patch-notes
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/patch-notes
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill patch-notes-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns release history, sprint notes, and changelog fragments into polished patch notes, saving time and keeping public updates consistent.

Core Features & Use Cases

  • Data gathering: Reads changelogs, git history, sprint retrospectives, and related product artifacts to build a complete release picture.
  • Audience-aware drafting: Adapts tone and structure for players or developers, including breaking changes, fixes, deprecations, and known issues where relevant.
  • Use case: Use it when you need a release summary for a new version and want the notes organized, audience-appropriate, and ready for review.

Quick Start

Ask the skill to generate patch notes for the target version using the available changelog and repository history.

Frequently Asked Questions about patch-notes

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

FAQPage Schema
How do I generate release notes from git commit history and changelog fragments?

Generate release notes by feeding git history and changelog fragments to the skill, which reads the data to build a complete release picture and drafts an organized summary. It categorizes changes into fixes, deprecations, and known issues.

Can I create player-facing patch notes for game releases?

Yes, you can create player-facing patch notes for game releases using audience-aware drafting features. The skill adapts tone and structure for players or developers, ensuring the summary is appropriate for the target audience.

What's the best way to structure breaking changes and migration notes in version documentation?

Structure breaking changes and migration notes using review-safe output with categorized sections. The skill detects tone guidance and applies templates to organize deprecations, impacts, and known issues where relevant for developer-facing summaries.

How do I turn sprint retrospectives and changelog fragments into a version summary?

Turn sprint retrospectives and changelog fragments into a version summary by providing them as input data. The skill gathers context from these product artifacts to draft audience-appropriate, review-ready release notes.

Does this approach work for both developer-facing and player-facing release summaries?

Yes, this approach works for both developer-facing and player-facing release summaries. The skill applies tone guidance detection to adapt the output structure, ensuring the patch notes meet the specific needs of developers or players.

What limitations exist when drafting patch notes from repository history?

A limitation when drafting patch notes is that the skill requires available changelog data and repository history to function. Without sufficient context from sprint notes or git history, it cannot generate a complete and accurate release summary.