changelog

Compile structured changelogs from git commits, sprint reports, and design documents.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill changelog-johnatas-henrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/changelog
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill changelog-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually compiling changelogs from scattered git commits, sprint reports, and design documents is time-consuming and often leads to inconsistencies between internal team notes and public player-facing updates. This Skill eliminates that manual effort by automating the entire changelog generation process.

Core Features & Use Cases

  • Dual Changelog Output: Generates both detailed internal changelogs for development teams and polished, player-friendly changelogs ready for public release.
  • Automated Data Aggregation: Pulls change data directly from git logs, sprint reports stored in production/sprints/, and completed design documents in design/gdd/ to ensure no relevant changes are missed.
  • Intelligent Categorization: Automatically sorts changes into clear categories (new features, improvements, bug fixes, balance changes, etc.) and tracks key metrics like total commits and commits missing task references. Use Case: For a game studio releasing a new sprint update, use this Skill to quickly compile a comprehensive changelog that aligns internal development context with the public patch notes shared with players.

Quick Start

Use the changelog skill to generate a full changelog for the latest sprint or your specified version.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I auto-generate changelogs from git commit history and sprint reports?

This Skill automates changelog generation by pulling data directly from git commit history, sprint reports, and design documents to compile structured internal and public-facing release notes.

What is the best way to create both internal and public release notes for a game development sprint?

The best way is to use an automated dual-output changelog generator that compiles detailed internal team notes alongside polished, player-friendly patch notes from your sprint and game design documents.

Can I automatically categorize git commits into features, improvements, and bug fixes for documentation?

Yes, automated changelog compilation intelligently sorts changes from git logs into clear categories like new features, improvements, and bug fixes while tracking metrics for commit coverage.

Does automated changelog generation work with game design documents stored in my project?

Yes, automated changelog generation pulls change data directly from completed game design documents in your design directory alongside git logs and sprint reports to ensure no updates are missed.

How do I track commits missing task references when compiling sprint release notes?

Automated changelog generation tracks key metrics including total commits and commits missing task references, ensuring your sprint release notes maintain proper alignment with project tasks.