agentleFS
Sign inStart free
elmohqelmohq/elmo/.claude/skills/add-changeset/SKILL.md

add-changeset

Skill577 starsChanged 19 days agoMITView on GitHub

Create a changeset file in .changeset/ that describes a user-facing change for the release notes

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. swc-project/swc★ 34ksame name
    2. OpenZeppelin/openzeppelin-contracts★ 27ksame name
    3. OpenZeppelin/openzeppelin-contracts-upgradeable★ 1.2ksame name
    4. hashicorp/design-system★ 520same name
    5. unional/skills★ 1same name

    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.

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    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:

    Create a markdown file in .changeset/ documenting a user-facing change.

    line 8
  2. Distinctive:

    Consider a changeset for any PR, but write one only for *user-facing* changes — skip pure refactors and docs-only changes.

    line 12
  3. Distinctive:

    Keep it to one concise sentence — roughly 160 characters or fewer.

    line 33
  4. Very specific:

    Check existing files in .changeset/ or recent CHANGELOG.md entries for examples.

    line 39

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

Create a markdown file in .changeset/ documenting a user-facing change.

When to create one

Consider a changeset for any PR, but write one only for user-facing changes — skip pure refactors and docs-only changes. Describe how the change affects the user, not the implementation. Most PRs need a single changeset; multiple is rare but occasionally appropriate.

Filename

Pick something short and descriptive, the way you would choose a branch name (e.g. remove-cli-status.md).

Format

---
"@elmohq/cli": patch
"@workspace/docs": patch
---

Description of the change.

List only the packages affected. Default to patch unless the user asks for a different bump.

Writing the description

  • Keep it to one concise sentence — roughly 160 characters or fewer. Length signals importance, so scale it to the change, but err short.
  • Plain text — no headers, bold, italics, or newlines inside the description. Inline code with single backticks and links are fine when genuinely useful.
  • End every sentence with a full stop.
  • Past tense for what the PR did: "Added", "Fixed", "Changed".
  • Present tense for Elmo's behavior: "Elmo now supports…", "{feature} now…".

Check existing files in .changeset/ or recent CHANGELOG.md entries for examples.

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.

Check your setup, free