changelog
FeaturedAuto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
AI & Automation 40,030 stars
5224 forks Updated 1 weeks ago MIT
Install
Quality Score: 97/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
## Phase 1: Parse Arguments
Read the argument for the target version or sprint number. If a version is given, use the corresponding git tag. If a sprint number is given, use the sprint date range.
Verify the repository is initialized: run `git rev-parse --is-inside-work-tree` to confirm git is available. If not a git repo, inform the user and abort gracefully.
---
## Phase 2: Gather Change Data
Read the git log since the last tag or release:
```
git log --oneline [last-tag]..HEAD
```
If no tags exist, read the full log or a reasonable recent range (last 100 commits).
Read sprint reports from `production/sprints/` for the relevant period to understand planned work and context behind changes.
Read completed design documents from `design/gdd/` for any new features implemented during this period.
---
## Phase 3: Categorize Changes
Categorize every change into one of these categories:
- **New Features**: Entirely new gameplay systems, modes, or content
- **Improvements**: Enhancements to existing features, UX improvements, performance gains
- **Bug Fixes**: Corrections to broken behavior
- **Balance Changes**: Tuning of gameplay values, difficulty, economy
- **Known Issues**: Issues the team is aware of but have not yet resolved
- **Miscellaneous**: Changes that do not fit the above categories, or commits whose messages are too vague to classify confidently
For each commit, check whether the message contains a task ID or story reference
(e.g. `[STORY-123]`, `TR-`, `#...
Details
- Author
- Donchitos
- Repository
- Donchitos/Claude-Code-Game-Studios
- Created
- 9 months ago
- Last Updated
- 1 weeks ago
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
AI & Automation Listed
changelog
Write release notes or a CHANGELOG.md entry from git history. Use when the user says "write the changelog", "release notes for v2.3", "what changed since the last release/tag", or is preparing a release or version bump.
0 Updated 5 days ago
Kuan-AI-com AI & Automation Listed
changelog
Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.
6 Updated 2 months ago
tuliosousapro AI & Automation Listed
changelog
Use when the user wants to generate a changelog, release notes, or document what changed between versions, tags, or PRs
45 Updated 2 weeks ago
AlemTuzlak