changelog
Skill885 starsChanged 4 months agoMITView on GitHub
Invoke before committing user-facing JET changes such as features, bug fixes, compatibility changes, or deprecations. Skip internal refactors, CI or docs-only changes, and routine dependency bumps without user impact.
165 other projects use a version of this, 1 of them edited.
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 · 1
- aviatesk/JETLS.jl★ 32118% same
Wrote their own version · 164
- 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
154 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- commitSkill
- run-testSkill
- write-testSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 154 edited versions we read keep these.
5
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
- Very specific: line 17
Add new entries under ## [Unreleased].
- Distinctive: line 20
Use the established Keep a Changelog subsections as appropriate:
- Very specific: line 28
Use ### Internal only when maintainers intentionally want to record a notable internal change.
- Distinctive: line 34
Start Added entries with "Added ..." and Fixed entries with "Fixed ...".
- Distinctive: line 37
Use backticks for report types, function names, configuration names, and other code elements.
- Distinctive: line 44
Write entries from the user's perspective.
- Distinctive: line 47
Do not include lowered IR details, Compiler.jl hook methods, abstract interpretation state, or virtual-process internals unless users can …
“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
Updating CHANGELOG.md
Format
This project follows Keep a Changelog.
Section structure
Add new entries under ## [Unreleased]. Do not edit a released section unless
the user explicitly requests it.
Use the established Keep a Changelog subsections as appropriate:
### Addedfor new functionality### Changedfor changes to existing functionality or compatibility### Deprecatedfor features that will be removed### Removedfor removed functionality### Fixedfor bug fixes
Use ### Internal only when maintainers intentionally want to record a notable
internal change. Do not add empty subsections or introduce a new category when
an existing one fits.
Entry style
- Start Added entries with "Added ..." and Fixed entries with "Fixed ...".
- Describe Changed entries in terms of concrete behavior or compatibility.
- Refer to GitHub issues as
aviatesk/JET.jl#NNN. - Use backticks for report types, function names, configuration names, and other code elements.
- Record dependency changes when they affect supported Julia versions, compatibility, installation, or user-visible behavior. Omit routine bumps.
Entry content
Write entries from the user's perspective. Describe what changed in terms of user-visible behavior, not implementation details.
- Do not include lowered IR details, Compiler.jl hook methods, abstract interpretation state, or virtual-process internals unless users can reasonably observe or interact with them.
- The "why" of a fix rarely matters to users; the "what" does. If the prior behavior is worth mentioning, describe its user-visible symptom rather than its internal cause.
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.

