changelog

Generates internal and player-facing changelogs from git commits, sprint reports, and design documents.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill changelog-onemanking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/changelog
Command: npx skills add https://github.com/onemanking/the-operator --skill changelog-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes requires manually reviewing dozens of commits, sprint reports, and design docs, then translating technical changes into language players understand. This Skill automates that entire process, producing both a detailed internal changelog and a polished player-facing version. ## Core Features & Use Cases - Dual Changelog Generation: Produces a technical internal changelog (with commit hashes, owners, and metrics) and a friendly player-facing changelog from the same source data. - Multi-Source Context: Reads git history since the last tag, sprint reports from production/sprints/, and design documents from design/gdd/ to understand the intent behind changes. - Structured Categorization: Sorts every change into New Features, Improvements, Bug Fixes, Balance Changes, and Known Issues with design reasoning included. - Use Case: After finishing Sprint 12 of your game project, invoke the skill with the sprint number to get a ready-to-review internal changelog and a community-post-ready player announcement. ## Quick Start Ask the AI to generate the changelog for version 1.4 or for a specific sprint number using recent git history and sprint reports.

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 commits automatically?

Invoke the changelog skill with a version or sprint number. It reads git log since the last tag, cross-references sprint reports and design documents, then categorizes every change into features, improvements, bug fixes, and balance changes.

How to write player-facing release notes from technical commits?

The skill generates a separate player-facing changelog that translates technical changes into friendly, non-technical language. It excludes code references, file paths, and developer names while keeping design reasoning for balance changes.

What happens if my repository has no git tags?

If no tags exist, the skill falls back to reading the full git log or a reasonable recent range of the last 100 commits. It also verifies the directory is a git repository first and aborts gracefully if git is unavailable.

Does the changelog skill handle messy git history?

Yes. When history contains merge commits, reverts, or fixup commits, the skill cleans up the narrative and groups related changes together rather than listing every commit literally. Unclear commit messages are resolved using sprint data.

What information does the internal changelog include?

The internal changelog includes commit hashes, change owners, design doc links, balance change reasoning with old and new values, technical debt notes, known issues with severity, and metrics like files changed and lines added or removed.