changelog
Skill9 starsChanged 7 months agoMITView on GitHub
Generate changelog from git history and design docs. Roblox update log format.
166 other projects use a version of this.
Adopted by
Most recently taken up by
- deg/beads-utilstheir own version, first seen Nov 16, 2026
- raphaeltm/simple-agent-managertheir own version, first seen Nov 15, 2026
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- Kuan-AI-com/agent-skillstheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- rust-works/omni-devtheir own version, first seen Nov 15, 2026
Used with
Projects with it also use playtest-report, soak-test and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 12 projects that use this
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 9 projects that use this
lilangMaxSkillteam-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 9 projects that use this
CoralGameSkillteam-audio
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
Also in 12 projects that use this
- +5 more from lilangMax
- +2 more from CoralGame
Other versions166 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 166
- meteor/meteor★ 45ksame name
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- MaaAssistantArknights/MaaAssistantArknights★ 25ksame name
- pipecat-ai/pipecat★ 17ksame name
- elie222/inbox-zero★ 13ksame name
- hashicorp/terraform-provider-aws★ 11ksame name
- JetBrains/ideavim★ 10ksame name
- BuilderIO/agent-native★ 7.7ksame name
- UnigramDev/Unigram★ 5.5ksame name
- entireio/cli★ 5.3ksame name
156 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 repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 155 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Ask: "What range?" Options:
- Very specific: line 19
Default: since the last tag matching v*.
- Very specific: line 88
If the project has no CHANGELOG.md, offer to create one using Keep a Changelog format.
- Distinctive: line 91
Use past tense ("Added" not "Adds")
“Common” is measured: kept by at least 6 in 10 of the 155 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
/changelog — Generate Changelog
Delegate to: release-manager (with writer for language polish)
Steps
1. Determine Range
Ask: "What range?" Options:
- Since last release (tag or branch)
- Since last commit of type N
- Custom date range
- Custom commit range
Default: since the last tag matching v*.
2. Gather Git History
# Get commits since last tag
git log $(git describe --tags --abbrev=0)..HEAD --format="%H %s"
# Or date range
git log --since="2 weeks ago" --format="%H %s"3. Categorize Commits
Parse conventional commit format (type(scope): description):
- feat: New features
- fix: Bug fixes
- perf: Performance improvements
- refactor: Code refactoring
- docs: Documentation
- test: Tests
- chore: Maintenance
- style: Formatting
Group commits by type.
4. Extract Design Doc Changes
Cross-reference with design docs that were updated:
git diff --name-only $(git describe --tags --abbrev=0)..HEAD -- design/Note any GDDs that changed — those probably correspond to feature work.
5. Generate Two Outputs
Technical Changelog (for team / docs)
# Changelog
## [Unreleased]
### Added
- combat: Add dodge mechanic (#42)
- shop: Add GamePass: VIP Membership (#43)
### Changed
- combat: Rebalance weapon damage curves (#44)
### Fixed
- datastore: Fix race condition in save logic (#45)
- ui: Fix shop button alignment on mobile portrait (#46)
### Performance
- combat: Reduce hit detection overhead by 40% (#47)
### Deprecated
- (none)
### Removed
- (none)
### Security
- remotes: Add rate limiting to purchase remote (#48)Player-Facing Patch Notes
(Handoff to /patch-notes for this — changelog is technical)
6. Output
Present the technical changelog. On approval, write to CHANGELOG.md (or append to existing).
If the project has no CHANGELOG.md, offer to create one using Keep a Changelog format.
Changelog Style
- Use past tense ("Added" not "Adds")
- One line per change
- Include issue/PR references
- Group related small changes
- Lead with user-facing impact, not implementation details
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.

