Changelog
Auto-generate a changelog from git commits and sprint data.
Install
npx skills add Donchitos/Claude-Code-Game-Studios --skill changelog -g -a claude-code -y- Repository
- Donchitos/Claude-Code-Game-Studios32.1k
- Category
- Git and review
- Updated
- 17d ago
- License
- MIT
- Context cost
- Mediumabout 2,469 tokens
- Runs scripts
- No, instructions only
What it does
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation
Automation mode: Resolve modes.automation (project.local.yaml →
project.yaml → default collaborative). Every AskUserQuestion call and
every file write follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Changelog
Recent History
Recent commits:
!git log --oneline -30 2>/dev/null || true
Recent tags (newest first):
!git tag --list --sort=-v:refname 2>/dev/null | head -5
Provenance check, before trusting the history above
The commits above may not belong to this game. This skill's history blocks are auto-resolved before the body runs, so the read has already happened, what this check governs is whether that output is usable, not whether it is fetched.
- Read the injected commit subjects above. If there are none, the log is empty or git is unavailable, skip this check: there is nothing to classify, and Phase 1's no-history branch is the right stop.
- Classify each one as Game (mechanics, content, balance, art, audio, UI, or a bug in those), Framework / maintenance (subjects naming skills, hooks, agents, the test plan, CI, or the framework's own docs), or Unclear, and treat Unclear as Framework.
- Decide from the counts:
- At least one Game commit → proceed using only those, and state how many of how many you used.
- Zero Game commits → stop, using the message below.
