agentleFS
Sign inStart free
LedgerHQLedgerHQ/ledger-live/.agents/skills/create-changeset/SKILL.md

create-changeset

Skill627 starsChanged 7 days agoMITView on GitHub

Create changesets for the ledger-live monorepo using @changesets/cli. Use when the user asks to add a changeset, prepare a release, or document package changes for a PR.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

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

    Create a .changeset/<adjective-noun-verb>.md file (human-readable random identifier, matching @changesets/cli convention) with this format:

    line 8

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

Create a .changeset/<adjective-noun-verb>.md file (human-readable random identifier, matching @changesets/cli convention) with this format:

---
"package-name": minor
---

Short description of the change

Package Names

Package names must match exactly what's in each package.json:

App / LibPackage name
Mobile applive-mobile
Desktop appledger-live-desktop
Common lib@ledgerhq/live-common
Coin modules@ledgerhq/coin-<name> (e.g. @ledgerhq/coin-sui)
Layer packagesThe folder gives the name (structure-flow naming), e.g. @domain/entity-contact, @features/flow-contacts
Other libsCheck the lib's package.json name field

Private and published packages

  • Layer packages are private. Every package under shared/, domain/, features/, devtools/ and support/ has "private": true and is never published to npm. .changeset/config.json sets privatePackages.version: true and tag: false: a changeset still bumps a private package's version and writes its CHANGELOG.md, but publishes and tags nothing. Name the changed layer packages in the changeset like any other package, together with the app (ledger-live-desktop, live-mobile) whose users see the change.
  • No changeset for development-only changes. A change that only touches support/ presets or devDependencies needs none, and neither do docs and skills.
  • Published packages are the @ledgerhq/* packages without "private": true in their package.json, almost all under libs/. Their changeset becomes an npm release.

Impact Levels

LevelWhen to use
minorThe minimum: new features, bug fixes, internal changes
majorBreaking changes (rare, requires discussion)
patchOnly in a PR based on a hotfix branch, never on develop

Description

  • One line, concise but descriptive
  • Format: <verb> <what> or conventional commit style
  • Examples:
    • Add portfolio analytics dashboard with performance metrics
    • Fix transaction signing issue on mobile
    • Flush mobile content card click analytics before opening links

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