Generate internal and player-facing changelogs from git commits and sprint reports.
npx skills add https://github.com/imclab/xrA1-swarm --skill changelog-imclab
Please help me install this Agent Skill. Skill: changelog Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/changelog Command: npx skills add https://github.com/imclab/xrA1-swarm --skill changelog-imclab
This Skill removes the friction of manually writing release notes by automatically compiling a changelog from your repository’s git history, sprint context, and design documents.
Ask the changelog skill to generate the internal and player-facing changelogs for the latest sprint by using the argument sprint number.
High-intent search queries and answers about installing and using this skill.
To generate release notes from git commits, aggregate your repository's commit history, sprint reports, and design documents for a specific version. The system classifies each commit into categories like features, improvements, and bug fixes, then outputs formatted markdown changelogs for both internal and player-facing audiences.
Categorizing git commits for a sprint retrospective involves classifying logs into structured buckets like New Features, Bug Fixes, Balance Changes, and Known Issues. By aggregating sprint reports and design documents, you produce a structured change summary that tracks total commits and identifies missing task references.
Yes, you can create both internal and player-facing changelogs from a single git tag. By resolving the git tag version and extracting the log, the system generates a detailed internal changelog for team tracking and a separate player-facing version ready for community posting.
To compile a changelog for a specific sprint date range instead of a git tag, provide the sprint number. The tool scans commits, sprint reports, and design documents that fall within that date range, categorizing them into structured buckets for your release notes.
When generating version documentation, supported commit classifications include New Features, Improvements, Bug Fixes, Balance Changes, Known Issues, and Miscellaneous. This categorization helps structure release notes and communicate changes clearly to both internal teams and players.
Yes, the changelog generation process tracks commits without task references. It performs per-commit classification and task-reference counting, including metrics like total commits and unlinked tasks in the internal changelog output to help teams identify missing documentation.
johnlindquistGenerate changelogs from git commits and history as release notes.
plurigridGenerate user-facing changelogs from git commit history.
kazukinagataAnalyze sprint performance metrics and generate retrospective insights from Notion task data.
MichaelSolatiGenerate categorized internal and player-facing changelogs from git history and sprint reports.
