Generate changelogs from git commits, sprint data, and design documents.
npx skills add https://github.com/rakhnianskii9/God-Godot --skill changelog-rakhnianskii9
Please help me install this Agent Skill. Skill: changelog Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/changelog Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill changelog-rakhnianskii9
Streamlines the creation of changelogs by aggregating git commits, sprint results, and design documents into a single, trustworthy report.
Run the changelog unit with a target version or sprint number to generate both internal and player-facing changelogs.
High-intent search queries and answers about installing and using this skill.
Auto-generating changelogs from git commits and sprint data requires aggregating commit history, sprint results, and design documents into a single formatted report. This process categorizes changes into features, improvements, fixes, known issues, and design notes for engineering teams.
Creating player-facing release notes from development commits involves compiling git history and sprint data into a clear, release-ready summary suitable for end-users. The generated output validates consistency and formats technical changes into accessible summaries for players.
Generating release notes that categorize features, fixes, and design notes requires phase-aware validation across git commits, sprints, and design documents. The process classifies changes into distinct categories with consistency checks to produce formatted internal and external reports.
Generating a changelog requires sprint data located under production/sprints and design documents under design/gdd. Access to this specific folder structure and git history is necessary to categorize changes accurately and produce both internal developer reports and player-facing release notes.
Using a changelog generator for software releases automates formatting by aggregating commits, sprints, and design documents. Running the generation process with a target version or sprint number outputs both internal engineering records and player-facing summaries without manual formatting.
Aggregating design documents into engineering changelogs ensures design work is tracked alongside code changes. Combining git history, sprint results, and design docs produces a comprehensive, trustworthy report that validates consistency across features, improvements, fixes, and design notes.
TheBBzGenerate user-facing changelogs from git commits between versions.
striderZAGenerate categorized changelogs from git commits, sprint reports, and design documents.
scomofoGenerate categorized release notes from git history for internal and player audiences.
MichaelSolatiGenerate categorized internal and player-facing changelogs from git history and sprint reports.
