Generate player-facing patch notes and internal changelogs from git tags and commits.
npx skills add https://github.com/fagemx/gstack-game --skill game-docs
Please help me install this Agent Skill. Skill: game-docs Source: https://github.com/fagemx/gstack-game/tree/main/skills/game-docs Command: npx skills add https://github.com/fagemx/gstack-game --skill game-docs
Releasing games involves manual, error-prone docs work. This Skill automates the generation of player-facing patch notes, an internal changelog, and updates to all project documentation after a release to keep everyone aligned.
Run the game-docs skill after a release to generate patch notes and update project documentation.
High-intent search queries and answers about installing and using this skill.
Automating release notes generation from git tags and commits involves reading repository history to produce player-facing patch notes and internal changelogs. This Skill parses commit data and outputs documentation artifacts to your shared project directory.
Generating player-facing patch notes for a game release is best handled by automatically extracting changes from git commits. This Skill converts raw repository history into concise markdown summaries tailored for players.
Updating project documentation and API docs after a release can be fully automated by reading and writing to repository files. This Skill performs a documentation sweep to update README, GDD, and API docs to reflect the latest changes.
Creating an internal changelog for QA and auditing from git history requires parsing commit messages and tags into a structured developer-facing log. This Skill generates a detailed markdown changelog for engineering reference.
Automating post-release documentation requires access to git tags and commits within your repository. This Skill reads version control history to generate patch notes and writes the resulting markdown artifacts back to your project directory.
Manual changelog generation leads to errors in game development because it relies on hand-copying changes from memory or scattered sources. Automating the process directly from git commits ensures documentation accurately reflects the release.
Arry8Parse Git history to generate Markdown changelogs in Keep a Changelog format.
plurigridGenerate user-facing changelogs from git commit history.
zach-sourceExecute multi-step workflows defined in Markdown files with argument passing.
gkganesh12Generate synchronized developer and client changelogs from git history and task trackers.
