agentleFS
frappefrappe/frappe-ui/.claude/skills/changeset/SKILL.md

changeset

Skill1.1k starsChanged 35 days agoMITView on GitHub

Decide whether a frappe-ui change needs a changeset, choose patch or minor, and write the release-note text in `.changeset/*.md`. Use before opening any frappe-ui PR that changes shipped files.

17 other projects use a version of this.

Trending

Less talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 0 mentionsApr 2026: 1 mentionMay 2026: 0 mentionsJun 2026: 3 mentionsJul 2026: 1 mentionAug 2026: 9 mentionsSep 2026: 1 mentionOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the frappe/frappe-ui repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about frappe/frappe-ui

The biggest 5 of 28 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 28

Talked about on GitHub (28 times).

On GitHub · 28

23 more on GitHub

Used with

Projects with it also use better-auth-best-practices, turborepo and 5 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.
  • anasahmed07Skill

    better-auth-best-practices

    Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.

    Also in 3 projects that use this

  • VercelSkill

    turborepo

    Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    humanizer

    Tone enforcement patterns for external-facing community responses

    Also in 5 projects that use this

  • SentrySkill

    deslop

    Strip AI-generated noise from the diff before pushing — extra comments a human wouldn't write, defensive try/catch in trusted code paths, casts to any, inline imports in Python, and other style inconsistencies with the surrounding file. Use this immediately before commit so the diff stays clean.

    Also in 3 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 3 projects that use this

  • GoogleSkill

    improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run yarn changeset and choose the bump.

    line 45
  2. Very specific:

    Write for an app developer who reads the changelog.

    line 61
  3. Very specific:

    Start with the component or area, such as Combobox or Tailwind preset.

    line 68
  4. Very specific:

    Do not end with a tag such as (fix) or (additive).

    line 70
  5. Distinctive:

    If the app must do something, say what in the same line.

    line 74
  6. Distinctive:

    Use one changeset per change.

    line 76

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

Changesets

A changeset is a Markdown file in .changeset/. It says how the next release bumps the version, and it holds the changelog text for the change. The release PR collects all pending changesets into CHANGELOG.md.

Does the PR need one?

The Verify changesets check decides. It fails when the PR changes a shipped file and adds no changeset. Shipped files are:

  • the files list in package.json, such as src/, vite/ and tailwind/,
  • the files list in packages/create-frappe-ui/package.json,
  • package.json and packages/create-frappe-ui/package.json.

Tests, stories, playgrounds and Markdown files do not count, even inside src/. Component docs such as src/components/Button/Button.md count as docs.

ChangeWhat to add
Apps see a differencea changeset with text
Refactor, types-only cleanup or dependency bump that apps do not seeyarn changeset --empty
Docs, CI, tests or specs onlynothing

Choose the bump

ChangeBump
Bug fix, or a visual or behavior correctionpatch
New public API: a component, prop, slot, event, export or tokenminor
Deprecation of a public APIminor
Breaking changeStop. Ask a maintainer. v1 takes no major release from a PR.

minor needs the release:minor label on the PR. A maintainer adds it. Without the label, the check fails. Say in the PR description why the change is minor.

Create the file

Run yarn changeset and choose the bump. Or write the file by hand with any name:

---
'frappe-ui': patch
---

Combobox: a picked option now commits before the popover closes.

Name frappe-ui only. A create-frappe-ui change also takes a frappe-ui changeset, because both packages share one version.

Write the text

Write for an app developer who reads the changelog. The text of each changeset becomes one line in CHANGELOG.md. Use this format:

<Component or area>: <what changed for the app>.
  • Start with the component or area, such as Combobox or Tailwind preset.
  • Say what changed for the app, not how the code changed.
  • Do not end with a tag such as (fix) or (additive). The release PR already puts each line under "Minor Changes" or "Patch Changes".
  • A deprecation ends with (deprecation), so it stands out from the new features under "Minor Changes", and says what to use instead.
  • If the app must do something, say what in the same line. Keep the text to one line.
  • Use one changeset per change. A PR with two independent changes adds two files.

Examples:

Combobox: a picked option now commits before the popover closes.
Dialog: the new `size` prop sets the width of the dialog.
Badge: the `theme` prop is deprecated; use `variant` instead (deprecation).

Releases

Maintainers release. Agents do not merge the release PR.

  1. Each merge to main updates the chore(release): version packages PR. It writes each changeset as one line in CHANGELOG.md, followed by a link to its PR (.changeset/changelog.cjs).
  2. Merging it changes the version. publish.yml publishes to npm, tags the commit, and creates a GitHub release from the version's CHANGELOG.md section.

The docs page /docs/changelog/v1 includes CHANGELOG.md, so it needs no copy. /docs/changelog/v0-to-v1 lists the changes up to 1.0.0 and does not change.

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.