agentleFS
aviateskaviatesk/JET.jl/.agents/skills/changelog/SKILL.md

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

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.
  • CoralGameSkill

    playtest-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

  • lilangMaxSkill

    soak-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

  • lilangMaxSkill

    team-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

  • CoralGameSkill

    team-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

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
  1. Very specific:

    Add new entries under ## [Unreleased].

    line 17
  2. Distinctive:

    Use the established Keep a Changelog subsections as appropriate:

    line 20
  3. Very specific:

    Use ### Internal only when maintainers intentionally want to record a notable internal change.

    line 28
  4. Distinctive:

    Start Added entries with "Added ..." and Fixed entries with "Fixed ...".

    line 34
  5. Distinctive:

    Use backticks for report types, function names, configuration names, and other code elements.

    line 37
  6. Distinctive:

    Write entries from the user's perspective.

    line 44
  7. Distinctive:

    Do not include lowered IR details, Compiler.jl hook methods, abstract interpretation state, or virtual-process internals unless users can …

    line 47

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  • ### Added for new functionality
  • ### Changed for changes to existing functionality or compatibility
  • ### Deprecated for features that will be removed
  • ### Removed for removed functionality
  • ### Fixed for 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.