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

changelog

Skill321 starsChanged 13 days agoMITView on GitHub

Invoke before committing user-facing changes (new features, bug fixes, behavior changes) to update CHANGELOG.md. Skip for internal refactors, CI, docs-only, or minor dependency bumps.

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

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the following subsections as needed (in this order):

    line 29
  2. Distinctive:

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

    line 38
  3. Very specific:

    When closing a GitHub issue, append (Closed https://github.com/aviatesk/JETLS.jl/issues/NNN).

    line 41
  4. Distinctive:

    Use backticks for diagnostic names, function names, and code elements.

    line 43
  5. Distinctive:

    Write entries from the user's perspective.

    line 47
  6. Distinctive:

    Don't include internal mechanisms (AST node types, specific JuliaLowering/JuliaSyntax internals, traversal strategies) unless a user could …

    line 50
  7. Distinctive:

    When adding a time-limited announcement, put a comment right above it recording when it was added and when it should be removed, typically …

    line 59
  8. Distinctive:

    If an announcement's removal date has passed, tell the user, and remove it together with its comment separately from the entry being added.

    line 72

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

Line length

CHANGELOG.md is exempt from the 80-character Markdown line length rule because it is used for GitHub release notes, where hard line breaks disrupt rendering.

That said, do not put everything on a single line unconditionally. Break lines at natural points (sentence boundaries, after colons, etc.) when an entry is long enough to benefit from it. Short, single-sentence entries are fine as one line.

Section structure

New entries go under the ## Unreleased section. Use the following subsections as needed (in this order):

  • ### Announcement -- important notices (always first if present)
  • ### Added -- new features
  • ### Changed -- changes to existing functionality
  • ### Fixed -- bug fixes

Entry style

  • Start Added entries with "Added ..." and Fixed entries with "Fixed ...".
  • Changed entries typically start with the component name (e.g. "lowering/undef-local-var now ...").
  • When closing a GitHub issue, append (Closed https://github.com/aviatesk/JETLS.jl/issues/NNN).
  • Use backticks for diagnostic names, function names, and code elements.

Entry content

Write entries from the user's perspective. Describe what changed in terms of user-visible behavior — not implementation details.

  • Don't include internal mechanisms (AST node types, specific JuliaLowering/JuliaSyntax internals, traversal strategies) unless a user could reasonably observe or interact with them.
  • The "why" of a fix rarely matters to users; the "what" of the new behavior does. If the prior behavior is worth mentioning, describe its user-visible symptom, not its cause.

Announcement lifetime

When adding a time-limited announcement, put a comment right above it recording when it was added and when it should be removed, typically one month later:

<!-- Added: 2026-10-11 / Remove after: 2026-11-11 -->
> [!note]
> ...

Announcements without a time limit, such as the supported Julia versions, have no such comment.

If an announcement's removal date has passed, tell the user, and remove it together with its comment separately from the entry being added.

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.