write-changelog
Skill39k starsChanged 7 days agoMITView on GitHub
Writes a changelog from git commits and sprint data. Use for an internal or player-facing one.
13 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- pahlevikun/levistacktheir own version, first seen Nov 1, 2026
- DataDog/dd-trace-rbtheir own version, first seen Oct 9, 2026
- jamiebrynes7/obsidian-todoist-plugintheir own version, first seen Oct 9, 2026
- petera2c/simple-tabletheir own version, first seen Oct 8, 2026
- classroomio/classroomiotheir own version, first seen Oct 8, 2026
- zulip/zuliptheir own version, first seen Oct 8, 2026
Who's talking about Donchitos/Claude-Code-Game-Studios
- Claudical“그림 파일 하나 없이 아이디어 한 줄로 만든 게임 | Claude Code Game Studios”YouTube · Oct 27, 2026 · 18k views
- Matheus Battisti“Criar jogos com IA ficou ABSURDO! (Claude Code com 49 agentes)”YouTube · Nov 2, 2026 · 5.6k views
- Chrono IT Channel“Letting 49 AI Agents Run a "Game Studio" — Claude Code Game Studios”YouTube · May 30, 2026 · 1.8k views
- AutomateNow“Claude Code Game Studios: Free Repo Turns Claude Code Into a 49-Agent Game Studio #Shorts”YouTube · Oct 30, 2026 · 1.4k views
- SkipCI“Claude Code Game Studios: 49 AI Agents, 74 Commands, Ranked Last in Blind Test”YouTube · Oct 31, 2026 · 1.4k views
The biggest 5 of 74 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 74
Talked about on GitHub, YouTube and Bluesky (74 times).
On GitHub · 39
- Nov 15, 2026Sync upstream v1.3.0 — spirit986/Claude-Code-Game-Studios0 reactions
- Nov 13, 2026add links — rumca-js/rumca-js.github.io0 reactions
- Nov 12, 2026게임 스튜디오 에이전트들 세분화 — arch-spatula/isekai-generator0 reactions
- Nov 10, 2026research: GitHub 오픈소스 10종 심층 비교 및 JARVIS 개발 세션 인계 (2026-11-10) — coddddin/jarvis-mcp0 reactions
- Nov 9, 2026feat(chaos-engine): game-studio follow-up from the 2026-11-09 study — ShaftHQ/SHAFT_ENGINE0 reactions · 2 comments
34 more on GitHub
- Nov 9, 2026agent-skills.github.donchitos.claude-code-game-studios: 1.2.0 → 1.3.0 — sudosubin/agents.nix0 reactions
- Nov 9, 2026Research: inventory external Unity game-dev skills for project-local adoption — AlvaGonz/A-B-Revival0 reactions · 1 comment
- Nov 9, 2026PROJECT MASTER DIRECTIVE — Dr-sOuL7/PlayGround0 reactions · 3 comments
- Nov 8, 2026[Future Isles] Reuse and validate upstream GameDev Skills (Phaser, game systems, Blender) — alston-personal/agentmanager0 reactions · 5 comments
- Nov 6, 2026[P1] Save the text of the golden pages to evals/golden/ — minhtran3124/mnemo0 reactions · 1 comment
- Nov 3, 2026[edition] 2026-11-03 18:00 — leoneoo/ai-lianmeng0 reactions · 1 comment
- Nov 3, 2026🔥 GitHub Trending AI 早报 · 2026-11-03 · Top 5 项目 — happydog-intj/ai-xiaohongshu-daily0 reactions
- Nov 3, 2026Github trending [Donchitos/Claude-Code-Game-Studios] 49个agent+74技能按真实工作室层级把Claude Code变游戏团队 — web1992/github-trending0 reactions
- Nov 2, 2026🔥 GitHub Trending AI 早报 · 2026-11-03 · Top 5 项目 — happydog-intj/ai-xiaohongshu-daily0 reactions
- Nov 2, 2026🔥 GitHub Trending AI 早报 · 2026-11-02 · Top 6 项目 — happydog-intj/ai-xiaohongshu-daily0 reactions
- Nov 2, 2026day-035: Claude Code Game Studios — CLAUDE.md auto-discoveryを発見 — Matsushima-A-830/ai-100days0 reactions
- Nov 2, 2026Github trending [Donchitos/Claude-Code-Game-Studios] 49个agent+74技能按真实工作室层级把Claude Code变游戏团队 — web1992/github-trending0 reactions
- Nov 1, 2026today: Day 035にClaude Code Game Studiosを設定 — Matsushima-A-830/ai-100days0 reactions
- Nov 1, 2026research: 2026-11-01分のネタ候補5件をbacklog.mdに追記 — Matsushima-A-830/ai-100days0 reactions
- Nov 1, 2026🔥 GitHub Trending AI 早报 · 2026-11-02 · Top 6 项目 — happydog-intj/ai-xiaohongshu-daily0 reactions
- Nov 1, 2026🔥 GitHub Trending AI 早报 · 2026-11-01 · Top 7 项目 — happydog-intj/ai-xiaohongshu-daily0 reactions
- Nov 1, 2026Github trending [Donchitos/Claude-Code-Game-Studios] 49子代理打造完整游戏工作室 — web1992/github-trending0 reactions
- Oct 31, 2026🔥 GitHub Trending AI 早报 · 2026-11-01 · Top 7 项目 — happydog-intj/ai-xiaohongshu-daily0 reactions
- Oct 30, 2026Donchitos 'Claude-Code-Game-Studios' — 49개 에이전트·74개 스킬로 Claude Code를 게임 개발 스튜디오로, 일간 트렌딩 진입 (10/29, GitHub) — roomedia/ax-trend0 reactions
- Oct 25, 2026Import Claude Code Game Studios into .claude — RoxorLoops1337/Games0 reactions · 1 comment
- Oct 21, 2026Skill mới cho agent: soát cân bằng, chống gian lận, soak/perf, bot chập chờn, phân loại chơi thử — nguyenbinhanltv/soul-land-mmo0 reactions
- Oct 19, 2026agent-skills.github.donchitos.claude-code-game-studios: 1.1.3 → 1.2.0 — sudosubin/agents.nix0 reactions
- Oct 15, 2026研究作者列出的 16 個遊戲引擎與 AI 專案;新增 economy-balance skill — a91453/railway-game-ios0 reactions
- Oct 13, 2026agent-skills.github.donchitos.claude-code-game-studios: 1.1.2 → 1.1.3 — sudosubin/agents.nix0 reactions
- Oct 3, 2026agent-skills.github.donchitos.claude-code-game-studios: 1.1.0 → 1.1.2 — sudosubin/agents.nix0 reactions
- Sep 26, 2026agent-skills.github.donchitos.claude-code-game-studios: init at 1.1.0 — sudosubin/agents.nix0 reactions
- Sep 25, 2026Add Game Studios, rohitg00, BaseGold, and MineSwap — CryptoSuess/FoutainOfYouth0 reactions
- Aug 6, 2026技能侦察 2026-08-06 01:00Z:+8 精选(220) — NyphSan/CursorSkill0 reactions
- Aug 5, 2026技能侦察 DIGEST 2026-08-05 21:00Z:+8 一致性/体素/动画与 AngelScript·Art Bible — NyphSan/CursorSkill0 reactions
- Apr 30, 2026docs: add shields.io badges to README.md / README.ja.md — kirin0198/aphelion-agents0 reactions
- Apr 18, 2026📱 SNS 콘텐츠 - 2026-04-18 16:10 KST — leaf468/autothreads0 reactions
- Apr 18, 2026🤖 AI 트렌드 리포트 - 2026-04-18 16:10 KST — leaf468/autothreads0 reactions
- Apr 6, 2026Audit candidate: Donchitos/Claude-Code-Game-Studios — xiaolai/nlpm0 reactions · 2 comments
- Mar 22, 2026Add game studio agent support to agent-tools (adapted from Claude-Code-Game-Studios) — Unwrenchable/agent-tools0 reactions
On YouTube · 23
- Oct 27, 2026그림 파일 하나 없이 아이디어 한 줄로 만든 게임 | Claude Code Game Studios — Claudical18k views · 9 comments
- Nov 2, 2026Criar jogos com IA ficou ABSURDO! (Claude Code com 49 agentes) — Matheus Battisti - Hora de Codar5.6k views · 8 comments
- May 30, 2026Letting 49 AI Agents Run a "Game Studio" — Claude Code Game Studios — Chrono IT Channel1.8k views · 3 comments
- Oct 30, 2026Claude Code Game Studios: Free Repo Turns Claude Code Into a 49-Agent Game Studio #Shorts — AutomateNow1.4k views · 3 comments
- Oct 31, 2026Claude Code Game Studios: 49 AI Agents, 74 Commands, Ranked Last in Blind Test — SkipCI1.4k views · 4 comments
18 more on YouTube
- Oct 31, 2026Claude Code Game Studios: một phiên làm việc, cả studio game — Anh Nguyen Quoc (C5)813 views
- Oct 28, 2026Turn Claude Code Into a Game Studio (Part 1) — AI → AGI → ASI801 views
- Apr 16, 2026Donchitos/Claude-Code-Game-Studios - Gource visualisation — Gourcer740 views
- Oct 15, 2026Claude Code Game Studios GitHub Overview: How Sequential AI Roles Manage Game Projects — Alex Hitt734 views
- Oct 31, 2026Claude Code Game Studios: one session, a full game studio — GitHub Unboxed609 views
- Oct 28, 20261 Claude Code Chat = A Whole Game Studio 🤯 — Gadget Drop282 views · 1 comment
- Oct 15, 2026Claude-Code-Game-Studios: virtual game studio with a single chat — Next Horizon191 views · 1 comment
- Oct 16, 2026Claude Code Game Studios: 49 AI Agents to Run Your One-Person Game Studio — Not That Number188 views
- Oct 29, 2026Donchitos/Claude-Code-Game-Studios — Turn Claude Code into a full game dev studio — 49 AI agents, 72 — Git Radar104 views
- Nov 1, 2026Make a game solo like a whole studio? 49 agents in Claude Code | GitHub Radar #12 #Shorts — KIEU STUDIO54 views · 1 comment
- Oct 22, 2026Claude Code como estudio de VIDEOJUEGOS 🎮 49 agentes: ¿mito o verdad? (Game Studios) — BarbuPrime IA | Claude Code Vs Codex32 views · 1 comment
- Oct 31, 2026Donchitos/Claude-Code-Game-Studios is trending on GitHub. — Nexbit Studio18 views
- Oct 30, 2026게임 개발 도와주는 AI? Claude Code Game Studios로 할 수 있는 것 — 딴삽스튜디오12 views
- Oct 29, 2026Claude-Code-Game-Studios ⭐ 28601 | +538 today #github #opensource #shell — Git Radar12 views
- Nov 3, 2026Claude Code Just Became a FULL Game Development Studio 🎮🤖 — The Clever Machine10 views
- Nov 2, 2026Claude Code as a 49-Agent Game Studio (and Why More Docs Lost) — GitHub AI Repo10 views
- Oct 31, 2026【AIが49人のゲーム会社に】Claude Code Game Studiosの入れ方と全6ステップ|作らせたいゲーム募集 — にくまるOSS研究所8 views
- Nov 3, 2026【Claude-Code-Game-Studios】49エージェントの"ゲーム開発スタジオ"に1画面ゲームを頼んだらminimalは38分で遊べる物・standardは8ドルで設計書9本 — さつきのOSS研究室4 views · 1 comment
On Bluesky · 12
- Apr 19, 2026【GitHubトレンド調査】 Claude Codeをゲーム開発スタジオに変貌させる「Claude-Code-Game-Studios」が登場。… — @woody-ai-tools.bsky.social10 likes and reposts
- Apr 15, 2026🎉 Celebrating! 🎉 (500+ new stars) 📦 Donchitos / Claude-Code-Game-Studios ⭐ 9,860 (+523) 🗒 Shell Turn Claude Code into a full game dev… — @github-trending.bsky.social4 likes and reposts · 1 reply
- May 19, 2026This is the project in question. github.com/Donchitos/Cl... Most of these projects feel like toys or performance art masquerading as useful… — @impossible.bsky.social3 likes and reposts · 2 replies
- Apr 19, 2026🎉 Celebrating! 🎉 (500+ new stars) 📦 Donchitos / Claude-Code-Game-Studios ⭐ 13,024 (+828) 🗒 Shell Turn Claude Code into a full game dev… — @github-trending.bsky.social3 likes and reposts · 1 reply
- Nov 1, 2026Claude-Code-Game-Studios — Turn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination… — @thestackradar.bsky.social2 likes and reposts
7 more on Bluesky
- Nov 1, 2026An entire game dev studio in one Claude session? 🎮 Claude-Code-Game-Studios turns Claude Code into an AI production studio: 49 agents, 72… — @thestackradar.bsky.social1 likes and repost
- Oct 31, 2026今日のGitHubトレンド Donchitos/Claude-Code-Game-Studios Claude Codeのセッションを擬似的なゲーム開発スタジオとして運用するためのツールです。… — @dailygithubtrends.bsky.social1 likes and repost
- Apr 21, 2026https://github.com/Donchitos/Claude-Code-Game-Studios — @tom-doerr.bsky.social1 likes and repost
- Apr 1, 2026Un studio de 48 agents IA spécialisés dans Claude Code : hiérarchie complète (directors, leads, specialists), workflows automatisés et… — @camilleroux.com1 likes and repost
- Nov 2, 2026💎 Hidden Gem! 💎 (1000+ new stars) 📦 Donchitos / Claude-Code-Game-Studios ⭐ 33,084 (+1,380) 🗒 Shell Turn Claude Code into a full game… — @github-trending.bsky.social0 likes and reposts · 1 reply
- Oct 29, 2026🎉 Celebrating! 🎉 (500+ new stars) 📦 Donchitos / Claude-Code-Game-Studios ⭐ 28,645 (+538) 🗒 Shell Turn Claude Code into a full game dev… — @github-trending.bsky.social0 likes and reposts · 1 reply
- May 19, 2026It was this one: github.com/Donchitos/Cl... — @dphrygian.com0 likes and reposts · 1 reply
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- zulip/zulip★ 26ksame name
- microsoft/vscode-pull-request-github★ 2.6ksame name
- classroomio/classroomio★ 1.7ksame name
- jamiebrynes7/obsidian-todoist-plugin★ 1.2ksame name
- DataDog/dd-trace-rb★ 417same name
- petera2c/simple-table★ 235same name
- kannandreams/agent-top★ 22same name
- plugyawn/armada★ 2same name
- wsm94/gi-claude-skills★ 2same name
- fabianmagrini/skills★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository82 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- design/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- src/CLAUDE.mdCLAUDE.md
- studio-tests/CLAUDE.mdCLAUDE.md
- adoptSkill
- architecture-decisionSkill
- architecture-reviewSkill
- art-bibleSkill
- asset-auditSkill
- asset-specSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- bug-triageSkill
- changelogSkill
- code-reviewSkill
- consistency-checkSkill
- content-auditSkill
- create-architectureSkill
- create-control-manifestSkill
- create-epicsSkill
- create-storiesSkill
- cutSkill
- day-one-patchSkill
- design-reviewSkill
- design-systemSkill
- dev-storySkill
- estimateSkill
- gate-checkSkill
- helpSkill
- hotfixSkill
- launch-checklistSkill
- localizeSkill
- map-systemsSkill
- milestone-reviewSkill
- next-stepSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- playtest-reportSkill
- project-settingsSkill
- project-stage-detectSkill
- propagate-design-changeSkill
- prototypeSkill
- qa-planSkill
- quick-designSkill
- regression-suiteSkill
- release-checklistSkill
- retrospectiveSkill
- reverse-documentSkill
- review-all-gddsSkill
- scope-checkSkill
- security-auditSkill
- settingsSkill
- setup-engineSkill
- skill-improveSkill
- skill-testSkill
- smoke-checkSkill
- soak-testSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
21 rules. 0 are common, 15 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
15
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Read the injected commit subjects above.
- Distinctive: line 62
If no commit in the range is this game's, say so and stop:
- Distinctive: line 89
Read the argument for the target version or sprint number.
- Distinctive: line 91
Verify the repository is initialized: run git rev-parse --is-inside-work-tree to confirm git is available.
- Distinctive: line 104
Read the git log since the last tag or release:
- Distinctive: line 110
If no tags exist, bound the range explicitly — git log --oneline -n 100.
- Distinctive: line 113
If 100 commits does not reach far enough back, say so and ask for a start ref rather than widening blindly.
- Very specific: line 116
Read sprint reports from production/sprints/ for the relevant period to understand planned work and context behind changes.
- Very specific: line 118
Read completed design documents from design/gdd/ for any new features implemented during this period.
- Distinctive: line 232
After presenting the changelogs, ask the user:
- Very specific: line 239
Check whether docs/CHANGELOG.md exists before asking.
- Distinctive: line 241
If the user selects [A]: append the new internal changelog entry to the top of the existing file (newest entries first).
- Distinctive: line 243
If the user selects [B]: overwrite the file with the new changelog.
- Distinctive: line 244
If the user selects [C]: stop here without writing.
- Very specific: line 246
After a successful write: Verdict: CHANGELOG WRITTEN — changelog saved to docs/CHANGELOG.md.
- Distinctive: line 247
If the user declines: Verdict: COMPLETE — changelog generated.
- Very specific: line 253
Use /patch-notes [version] to generate a styled, saved version for public release.
- Very specific: line 254
Use /release-checklist before publishing the changelog externally.
- Distinctive: line 258
Never expose internal code references, file paths, or developer names in the player-facing changelog
- Distinctive: line 260
If a commit message is unclear, check the associated files and sprint data for context
- Distinctive: line 263
If the git history is messy (merge commits, reverts, fixup commits), clean up the narrative rather than listing every commit literally
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
!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 question 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.
Filter per commit; a repo containing maintenance work is not a wrong repo. Every project on this framework accumulates commits touching hooks, CI and skills — the game repo is the framework repo, so stopping on them would fire on virtually every real project. The harm is those commits becoming release copy, and excluding them prevents that precisely.
This rule is kept identical to
/patch-notes' on purpose — the two read the same history for different audiences, and they must not disagree about whose history it is. Change both together.
The genuine wrong-history signal is different: Game commits naming a product that
design/ and the code root (src/, Assets/ or Source/) never mention. If you
see that, stop.
If no commit in the range is this game's, say so and stop:
"The git history in this repo does not appear to belong to [game]: 0 of the [N] recent commits are Game commits. The recent commits describe [what they actually describe]. I cannot generate a changelog from it — point me at the right history, or supply the change list directly."
Verdict: BLOCKED — stop here without generating a changelog.
Why this is a hard stop, not a warning. Framework-internal commits rendered as player copy read as real changes: a session-hook timeout becomes "Fixed an issue where progress from your last session could be lost on launch" in a game with no save system. That copy is fluent, plausible, and entirely false. A reader cannot tell the difference; only this check can.
Do not treat the preamble's existence as evidence. Injected output means the command ran, never that its subject is your game.
Both blocks are resolved before this skill runs. Use them as the starting point for Phase 2 rather than re-running the same commands.
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.
If there is no history to read — not a git repository, or no commits yet:
"No git history found. A changelog is built from commits — commit the work first, or supply the change list directly."
Verdict: BLOCKED — stop here without generating a changelog.
Phase 2: Gather Change Data
Read the git log since the last tag or release:
git log --oneline [last-tag]..HEADIf no tags exist, bound the range explicitly — git log --oneline -n 100. Do not
fall back to the full log: on an established repo that is thousands of lines for
a changelog covering one release, and the oldest of them are the least relevant.
If 100 commits does not reach far enough back, say so and ask for a start ref
rather than widening blindly.
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. Read them by section: find the headings you need with the Grep tool (pattern ^#, content mode) and Read those ranges with offset and limit.
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
- Technical Debt / Refactoring: Refactors and cleanup of the game's code that change nothing the player sees — a commit that says it refactors, cleans up or tidies, and names no fix, feature or tuning. Internal changelog only; never in the player-facing one
- 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-, #NNN, or similar). Count commits that lack any task reference
and include this count in the Phase 4 Metrics section as: Commits without task reference: [N].
Phase 4: Generate Internal Changelog
# Internal Changelog: [Version]
Date: [Date]
Sprint(s): [Sprint numbers covered]
Commits: [Count] ([first-hash]..[last-hash])
## New Features
- [Feature Name] -- [Technical description, affected systems]
- Commits: [hash1], [hash2]
- Owner: [who implemented it]
- Design doc: [link if applicable]
## Improvements
- [Improvement] -- [What changed technically and why]
- Commits: [hashes]
- Owner: [who]
## Bug Fixes
- [BUG-ID] [Description of bug and root cause]
- Fix: [What was changed]
- Commits: [hashes]
- Owner: [who]
## Balance Changes
- [What was tuned] -- [Old value -> New value] -- [Design intent]
- Owner: [who]
## Technical Debt / Refactoring
- [What was cleaned up and why]
- Commits: [hashes]
## Miscellaneous
- [Change that didn't fit other categories, or vague commit message]
- Commits: [hashes]
## Known Issues
- [Issue description] -- [Severity] -- [ETA for fix if known]
## Metrics
- Total commits: [N]
- Files changed: [N]
- Lines added: [N]
- Lines removed: [N]
- Commits without task reference: [N]Phase 5: Generate Player-Facing Changelog
# What is New in [Version]
## New Features
- **[Feature Name]**: [Player-friendly description of what they can now do
and why it is exciting. Focus on the experience, not the implementation.]
## Improvements
- **[What improved]**: [How this makes the game better for the player.
Be specific but avoid jargon.]
## Bug Fixes
- Fixed an issue where [describe what the player experienced, not what was
wrong in the code]
- Fixed [player-visible symptom]
## Balance Changes
- [What changed in player-understandable terms and the design intent.
Example: "Healing potions now restore 50 HP (up from 30) -- we felt
players needed more recovery options in late-game encounters."]
## Known Issues
- We are aware of [issue description in player terms] and are working on a
fix. [Workaround if one exists.]
---
Thank you for playing! Your feedback helps us make the game better.
Report issues at [link].Phase 6: Output
Output both changelogs to the user. The internal changelog is the primary working document. The player-facing changelog is ready for community posting after review.
Phase 7: Offer File Write
After presenting the changelogs, ask the user:
"May I write this changelog to
docs/CHANGELOG.md? [A] Yes, append this entry (recommended if the file already exists) [B] Yes, overwrite the file entirely [C] No — I'll copy it manually"
- Check whether
docs/CHANGELOG.mdexists before asking. If it does, default the recommendation to [A] append. - If the user selects [A]: append the new internal changelog entry to the top of the existing file (newest entries first).
- If the user selects [B]: overwrite the file with the new changelog.
- If the user selects [C]: stop here without writing.
After a successful write: Verdict: CHANGELOG WRITTEN — changelog saved to docs/CHANGELOG.md.
If the user declines: Verdict: COMPLETE — changelog generated.
Phase 7: Next Steps
- Use
/patch-notes [version]to generate a styled, saved version for public release. - Use
/release-checklistbefore publishing the changelog externally.
Guidelines
- Never expose internal code references, file paths, or developer names in the player-facing changelog
- Group related changes together rather than listing individual commits
- If a commit message is unclear, check the associated files and sprint data for context
- Balance changes should always include the design reasoning, not just the numbers
- Known issues should be honest — players appreciate transparency
- If the git history is messy (merge commits, reverts, fixup commits), clean up the narrative rather than listing every commit literally
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

