agentleFS
Sign inStart free
purpleeddypurpleeddy/cladding/skills/changelog/SKILL.md

changelog

Skill16 starsChanged 4 months agoMITView on GitHub

Render release notes / a changelog from the cladding spec. Use when the user asks for release notes, a changelog, 릴리즈 노트, 변경 이력, or "what changed (since <ref>)" — run `clad changelog --json` for the deterministic shipped-changes manifest, then write the human-facing notes FROM it, sourcing every claim from a feature title or acceptance sentence. For audit asks, print the --audit table verbatim. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 144 edited versions we read keep these.

  • 1

    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:

    Collect: Run clad changelog --json --since <ref> (omit --since to use the latest tag.

    line 16
  2. Distinctive:

    Never invent a change, never embellish beyond what an AC states.

    line 24
  3. Very specific:

    Put unsharded_commits under an "Also changed" section, marked as not yet spec-tracked.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 144 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

Cladding changelog — release notes from the spec

The spec is the SSoT, so "what shipped?" is collected, never recalled. clad changelog turns <since>..HEAD into a deterministic manifest: feature shards classified (added-as-done / flipped-to-done / modified-while-done / archived), grouped by capability (plus an uncategorized bucket — itself a drift signal), the spec inventory diff, and conventional feat:/fix: commits that name no feature id (work that shipped outside the spec — report it honestly, don't hide it).

Protocol

  1. Collect. Run clad changelog --json --since <ref> (omit --since to use the latest tag; if the repo has no tags the command says so — ask the user for a ref).
  2. Render EN + KO release notes from the manifest, in the CHANGELOG.md house style:
    • Open with a **In one line:** abstract (what a user gains, one breath).
    • Group by the manifest's capability groups; use user-impact verbs ("the gate now runs your entry point"), not implementation verbs ("refactored stage runner").
    • No F-…/AC-… ids in prose (Soft Shell policy) — ids belong to the audit surface only.
    • Source every claim from the manifest — a feature title or an acceptance[] sentence. Never invent a change, never embellish beyond what an AC states. If the manifest is empty, say "no shipped changes since <ref>" — that line is the honest deliverable.
    • Put unsharded_commits under an "Also changed" section, marked as not yet spec-tracked.
  3. Audit asks ("show verification", "어디까지 검증됐어?") → print clad changelog --audit --since <ref> verbatim — that table keeps ids and marks every verification ref resolved ✓ / unresolved ✗ (a ✗ is spec-annotation drift worth reporting).
  4. Catalog asks ("what does this project do, in full?") → clad changelog --catalog prints the whole capability → feature → acceptance listing of the living spec.
clad changelog                       # markdown since the latest tag (deterministic fallback)
clad changelog --json --since v0.5.2 # the manifest you render notes from
clad changelog --audit --since v0.5.2
clad changelog --catalog

Download now (ZIP)

  • Other versions154 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 154

    1. meteor/meteor★ 45ksame name
    2. Donchitos/Claude-Code-Game-Studios★ 27ksame name
    3. MaaAssistantArknights/MaaAssistantArknights★ 24ksame name
    4. pipecat-ai/pipecat★ 17ksame name
    5. elie222/inbox-zero★ 13ksame name
    6. hashicorp/terraform-provider-aws★ 11ksame name
    7. JetBrains/ideavim★ 10ksame name
    8. BuilderIO/agent-native★ 7.6ksame name
    9. UnigramDev/Unigram★ 5.5ksame name
    10. entireio/cli★ 5.3ksame name

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

  • Used alongsideProjects 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 12 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 9 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 9 projects that use this

    • CoralGameSkill

      team-polish

      Orchestrate the polish team: coordinates performance-analyst, technical-artist, sound-designer, and qa-tester to optimize, polish, and harden a feature or area for release quality.

      Also in 14 projects that use this

    • +5 more from lilangMax
    • +3 more from CoralGame
  • In this repository17 other files it gives its agents.

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.

Check your setup, free