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
Most recently taken up by
- venhdev/skillstheir own version, first seen Nov 8, 2026
- louisbrulenaudet/monorepo-templatetheir own version, first seen Oct 29, 2026
- reactive/data-clienttheir own version, first seen Oct 9, 2026
- yamcodes/arkenvtheir own version, first seen Oct 8, 2026
- whitphx/stlitetheir own version, first seen Oct 8, 2026
- deadlock-mod-manager/deadlock-mod-managertheir own version, first seen Oct 8, 2026
Who's talking about frappe/frappe-ui
- frappe/helpdesk“feat!: customer contact management”GitHub · Feb 20, 2026 · 13 reactions
- frappe/frappe“feat: Billing Page”GitHub · Nov 14, 2024 · 9 reactions
- frappe/frappe“feat: PhoneInput component”GitHub · Jun 8, 2026 · 5 reactions
- frappe/helpdesk“feat: Dashboard”GitHub · Jun 13, 2025 · 5 reactions
- frappe/frappe“feat(user_invitation): add InviteUser UI block to @framework/ui”GitHub · Jun 30, 2026 · 4 reactions
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
- Feb 20, 2026feat!: customer contact management — frappe/helpdesk13 reactions · 13 comments
- Nov 14, 2024feat: Billing Page — frappe/frappe9 reactions · 5 comments
- Jun 8, 2026feat: PhoneInput component — frappe/frappe5 reactions · 2 comments
- Jun 13, 2025feat: Dashboard — frappe/helpdesk5 reactions
- Jun 30, 2026feat(user_invitation): add InviteUser UI block to @framework/ui — frappe/frappe4 reactions · 2 comments
23 more on GitHub
- Oct 27, 2025feat!: upgrade frappe-ui (`0.1.186` to `0.1.213`) - add Link, Combobox, TimePicker components — frappe/studio4 reactions
- Jan 7, 2024feat: List View Footer to control pagination — frappe/crm4 reactions
- Dec 23, 2025feat!: upgrade frappe-ui (0.1.213 to 0.1.245) - add MonthPicker, MultiSelect, Filter & more — frappe/studio3 reactions
- Nov 1, 2025refactor: reduce bundle size — frappe/helpdesk3 reactions
- Feb 19, 2025fix: Trial banner & Login to FC — frappe/crm3 reactions · 1 comment
- Apr 14, 2026feat: Upgrade Frappe UI to latest version — frappe/press2 reactions · 1 comment
- May 26, 2025fix: replace deep imports from frappe-ui — frappe/press2 reactions · 2 comments
- Oct 12, 2026fix(mobile): run the bottom nav to the screen edge in an installed iOS 26 app — frappe/gameplan1 reaction · 3 comments
- Sep 22, 2026fix(ui): build against frappe-ui 1.0.0-rc.1 — frappe/frappe1 reaction · 1 comment
- Aug 7, 2026Upgrading to frappe-ui 1.0.0 — frappe/central1 reaction · 1 comment
- Aug 6, 2026Fix a batch of feedback: gray hover states, safer confirms, navigation, and one image upload path — frappe/gameplan1 reaction · 2 comments
- Jul 9, 2026refactor(framework/ui): move <Component>Props and <Component>Slots interfaces in .ts files — frappe/frappe1 reaction · 2 comments
- Jun 10, 2026refactor: List View filters and Custom Views — frappe/helpdesk1 reaction · 2 comments
- Dec 2, 2024fix: Replace translation with frappeui translation plugin — frappe/crm1 reaction
- Aug 8, 2026Upgrading to frappe-ui 1.0.0 — frappe/frappe-ui-starter0 reactions
- Aug 7, 2026Upgrading @framework/ui to frappe-ui 1.0.0 — frappe/frappe0 reactions · 4 comments
- Aug 7, 2026Upgrading to frappe-ui 1.0.0 — frappe/suite0 reactions · 11 comments
- Aug 7, 2026Upgrading to frappe-ui 1.0.0 — frappe/insights0 reactions · 6 comments
- Aug 7, 2026Upgrading to frappe-ui 1.0.0 — frappe/crm0 reactions · 13 comments
- Aug 7, 2026Upgrading to frappe-ui 1.0.0 — frappe/helpdesk0 reactions · 9 comments
- Aug 7, 2026Upgrading to frappe-ui 1.0.0 — frappe/gameplan0 reactions · 3 comments
- Feb 25, 2026Bump frappe-ui version to 1.0 (beta atm) — fossunited/fossunited0 reactions · 3 comments
- Feb 20, 2026Images get saved as base64 if no prior changes have been made in the editor — frappe/suite0 reactions
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.
anasahmed07Skillbetter-auth-best-practices
Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.
Also in 3 projects that use this
VercelSkillturborepo
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 AzureSkillhumanizer
Tone enforcement patterns for external-facing community responses
Also in 5 projects that use this
SentrySkilldeslop
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 CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 3 projects that use this
GoogleSkillimprove-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
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- withastro/astro★ 64ksame name
- biomejs/biome★ 26ksame name
- udecode/plate★ 17ksame name
- reactive/data-client★ 2ksame name
- whitphx/stlite★ 1.7ksame name
- MaxGfeller/open-harness★ 611same name
- deadlock-mod-manager/deadlock-mod-manager★ 584same name
- udecode/better-convex★ 452same name
- yamcodes/arkenv★ 151same name
- vobase/vobase★ 60same name
7 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.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- frappe-uiSkill
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
- Very specific: line 45
Run yarn changeset and choose the bump.
- Very specific: line 61
Write for an app developer who reads the changelog.
- Very specific: line 68
Start with the component or area, such as Combobox or Tailwind preset.
- Very specific: line 70
Do not end with a tag such as (fix) or (additive).
- Distinctive: line 74
If the app must do something, say what in the same line.
- Distinctive: line 76
Use one changeset per change.
“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.
Files
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
fileslist inpackage.json, such assrc/,vite/andtailwind/, - the
fileslist inpackages/create-frappe-ui/package.json, package.jsonandpackages/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.
| Change | What to add |
| Apps see a difference | a changeset with text |
| Refactor, types-only cleanup or dependency bump that apps do not see | yarn changeset --empty |
| Docs, CI, tests or specs only | nothing |
Choose the bump
| Change | Bump |
| Bug fix, or a visual or behavior correction | patch |
| New public API: a component, prop, slot, event, export or token | minor |
| Deprecation of a public API | minor |
| Breaking change | Stop. 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
ComboboxorTailwind 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.
- Each merge to
mainupdates thechore(release): version packagesPR. It writes each changeset as one line inCHANGELOG.md, followed by a link to its PR (.changeset/changelog.cjs). - Merging it changes the version.
publish.ymlpublishes to npm, tags the commit, and creates a GitHub release from the version'sCHANGELOG.mdsection.
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.
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
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.

