changelog

Generate changelogs from git history, sprint reports, and design documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns scattered repository history into a clear, structured changelog, saving you from manually reconciling commits, sprint notes, and design updates.

Core Features & Use Cases

  • Internal changelog generation: Builds a detailed working changelog from git commits, sprint reports, and completed design documents.
  • Public-facing release notes: Produces a cleaner, audience-appropriate changelog for users or developers after the internal draft is complete.
  • Repository-aware release reporting: Handles both product and game-style release taxonomy, including breaking changes, security, balance changes, and known issues.
  • Approval-based file writing: Prepares content first and only writes to docs/CHANGELOG.md after explicit user approval.

Quick Start

Ask the changelog skill to generate a changelog for the latest release and review the internal and public drafts before approving any file write.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate a changelog from git commit history and sprint reports?

Yes, you can generate a changelog for game repositories. The Skill handles game-style release taxonomy, including specific categories like balance changes, breaking changes, security updates, and known issues alongside standard features and fixes.

How do I write release notes without manually reconciling commits and design documents?

You can produce release notes automatically by feeding repository history and supporting project artifacts into the Skill. It reconciles the scattered data to classify changes and drafts audience-appropriate public notes after the internal working changelog is complete.

Do I need to approve file writes when generating a changelog to docs/CHANGELOG.md?

Yes, explicit approval is required before writing to docs/CHANGELOG.md. The Skill prepares the internal and public-facing content first, ensuring you can review the generated drafts before any file modifications happen.

What's the best way to create both internal and public-facing release notes from git history?

The best way is using a Skill that processes git commits and sprint reports to build a detailed internal changelog first, then produces a cleaner, audience-appropriate version for public release notes after your review.

Does this changelog generator work with product repositories that need detailed release summaries?

Yes, it works with product repositories needing internal release summaries. The Skill requires repository access and commit history to classify changes and measure impact, applying to both product and game-style release documentation workflows.