changelog
Skill2 starsChanged 2 months agoMITView on GitHub
Updates CHANGELOG.md in the Keep a Changelog format, adding the current changes under the Unreleased section. Use this when the user asks to update the changelog, add a changelog entry, or record what changed for the release notes (e.g. "add this to the changelog", "update CHANGELOG for these commits").
165 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 10 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 13 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 10 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 10 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 13 projects that use this
- +6 more from lilangMax
- +2 more from CoralGame
Other versions165 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 165
- 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
155 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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- commitSkill
- configure-repoSkill
- copywritingSkill
- design-system-auditSkill
- i18n-paritySkill
- identitySkill
- instantiateSkill
- migration-guardSkill
- new-adrSkill
- new-specSkill
- open-issueSkill
- open-prSkill
- port-changeSkill
- prototypeSkill
- releaseSkill
- seo-auditSkill
- update-templateSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 154 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Add the current changes to CHANGELOG.md.
- Very specific: line 8
Read CHANGELOG.md to match its existing style and confirm it follows Keep a Changelog (https://keepachangelog.com).
- Distinctive: line 17
Write entries as concise, user-facing bullet points (what changed and why it matters), not raw commit messages.
- Very specific: line 18
If the change implements a spec, also tick the item its proposal.md declares in the _Roadmap item_ field inside docs/product/roadmap.md — …
- Distinctive: line 23
Do NOT cut a versioned release (do not move Unreleased into a dated version) unless the user explicitly asks.
“Common” is measured: kept by at least 6 in 10 of the 154 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
Add the current changes to CHANGELOG.md.
- Read
CHANGELOG.mdto match its existing style and confirm it follows Keep a Changelog (https://keepachangelog.com). Ensure an## [Unreleased]section exists at the top; create it if missing. - Determine what changed since the last release: review recent commits (
git log <last-tag>..HEAD --oneline) and/or the working diff. - Summarize changes into the standard categories under Unreleased, creating only the subsections that apply:
Added— new features.Changed— changes to existing behavior.Deprecated— soon-to-be-removed features.Removed— removed features.Fixed— bug fixes.Security— vulnerability fixes.
- Write entries as concise, user-facing bullet points (what changed and why it matters), not raw commit messages. Link issues/PRs if the file does so.
- If the change implements a spec, also tick the item its
proposal.mddeclares in the Roadmap item field insidedocs/product/roadmap.md— CHANGELOG and roadmap travel in the same PR (docs/conventions/workflow.md, rules 5 and 6). - Report the lines you added.
Example: under ### Fixed → - Prevent crash when saving an empty form (#142).
Do NOT cut a versioned release (do not move Unreleased into a dated version) unless the user explicitly asks. Do NOT bump version numbers on your own.
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.

