changeset
Skill19 starsChanged 18 days agoApache-2.0View on GitHub
USE WHEN: a change under apps/ or packages/ (or an app runtime dependency bump) needs its release note, the user asks to add, fix, or check a changeset, a PR is about to open, or `pnpm release:check` fails. DO NOT USE WHEN: editing the release pipeline itself (.changeset/config.json, release.yml, the check scripts) - rule ops/release.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- getlien/lientheir own version, first seen Nov 15, 2026
- venhdev/skillstheir own version, first seen Nov 8, 2026
- frappe/frappe-uitheir own version, first seen Oct 17, 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
Used with
Projects with it also use better-auth-best-practices, humanizer and 3 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
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 versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- withastro/astro★ 64ksame name
- biomejs/biome★ 26ksame name
- udecode/plate★ 17ksame name
- reactive/data-client★ 2ksame name
- whitphx/stlite★ 1.7ksame name
- frappe/frappe-ui★ 1.1ksame name
- MaxGfeller/open-harness★ 611same name
- deadlock-mod-manager/deadlock-mod-manager★ 584same name
- udecode/better-convex★ 452same name
- yamcodes/arkenv★ 151same name
8 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 repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- hooks/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- hooks/CLAUDE.mdCLAUDE.md
- .cursor/rules/backend/hono-gateway.mdcCursor rule
- .cursor/rules/backend/ports.mdcCursor rule
- .cursor/rules/backend/service-bindings.mdcCursor rule
- .cursor/rules/backend/workers-cache.mdcCursor rule
- .cursor/rules/backend/workers-config.mdcCursor rule
- .cursor/rules/contracts/contracts.mdcCursor rule
- .cursor/rules/core/agent-instructions.mdcCursor rule
- .cursor/rules/core/boundaries.mdcCursor rule
- .cursor/rules/core/guardrails.mdcCursor rule
- .cursor/rules/core/turborepo.mdcCursor rule
- .cursor/rules/core/worktrees.mdcCursor rule
- .cursor/rules/frontend/react.mdcCursor rule
- .cursor/rules/frontend/tailwind.mdcCursor rule
- .cursor/rules/frontend/tanstack-query.mdcCursor rule
- .cursor/rules/frontend/tanstack-router.mdcCursor rule
- .cursor/rules/frontend/vite-config.mdcCursor rule
- .cursor/rules/ops/cd.mdcCursor rule
- .cursor/rules/ops/changesets.mdcCursor rule
- .cursor/rules/ops/ci.mdcCursor rule
- .cursor/rules/ops/previews.mdcCursor rule
- .cursor/rules/ops/quality-report.mdcCursor rule
- .cursor/rules/ops/release.mdcCursor rule
- .cursor/rules/quality/code-style.mdcCursor rule
- .cursor/rules/quality/comments.mdcCursor rule
- .cursor/rules/quality/knip.mdcCursor rule
- .cursor/rules/quality/lint-config.mdcCursor rule
- .cursor/rules/quality/markdown-style.mdcCursor rule
- .cursor/rules/quality/naming.mdcCursor rule
- .cursor/rules/quality/reporting.mdcCursor rule
- .cursor/rules/quality/simplicity.mdcCursor rule
- .cursor/rules/quality/testing.mdcCursor rule
- .cursor/rules/quality/typescript-config.mdcCursor rule
- .cursor/rules/tests/front-react.mdcCursor rule
- .cursor/rules/tests/hono-workers.mdcCursor rule
- cfSkill
- front-vitestSkill
- git-commitSkill
- honoSkill
- monorepo-agent-setupSkill
- pnpmSkill
- react-doctorSkill
- reviewSkill
- review-stackSkill
- run-appSkill
- security-auditSkill
- skills-updateSkill
- tanstack-configSkill
- tanstack-querySkill
- tanstack-routerSkill
- turborepoSkill
- ui-ux-design-best-practicesSkill
- vercel-react-best-practicesSkill
- workers-best-practicesSkill
- skills-updateSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Scope: Read the branch diff (git diff origin/main...HEAD --stat, plus uncommitted work) and split it into the changes a user or operator of …
- Very specific: line 15
never major unless the user asked for a breaking release.
- Very specific: line 27
Use --minor in the same form, or pnpm changeset --empty -m '<one-line reason>'.
“Common” is measured: kept by at least 6 in 10 of the 15 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
Changeset
Writing, bump, and frontmatter rules live in rule ops/changesets (.claude/rules/ops/changesets.md; Cursor: .cursor/rules/ops/changesets.mdc). Read it first if it is not already loaded; this skill is only the procedure.
- Scope. Read the branch diff (
git diff origin/main...HEAD --stat, plus uncommitted work) and split it into the changes a user or operator of a deployed app would notice. Note which apps each one reaches, including through a bundled@repo/*package or a runtime catalog bump. - Reuse.
git diff --name-only --diff-filter=AM origin/main -- .changeset/lists this branch's changesets. If one already covers a change, edit it instead of adding another. If the change fixes something still pending onmain, edit that pending changeset. - Decide per change, with the rule's tables:
- nothing observable ships:
--empty, or no changeset at all ifpnpm release:checkpasses without one; - otherwise
patchorminor, naming every app whose behavior changes and never an@repo/*package; - never
majorunless the user asked for a breaking release. While the apps are0.x, a breaking change isminorwith a**Breaking:**title.
- nothing observable ships:
Create one file per change, keeping the generated name:
pnpm changeset --patch worker-api,front-app -m "$(cat <<'EOF' Imperative title of at most 100 characters naming the surface in `backticks` Optional body: operator action, changed defaults, migration. EOF )"Use
--minorin the same form, orpnpm changeset --empty -m '<one-line reason>'.- Verify.
git add .changeset/<id>.md, thenpnpm release:check. Fix everychangesets(<rule>)line it prints and rerun until it exits 0.pnpm release:statusshows the resulting versions. - Report the file, the apps, and the bump in your reply and the PR description, and say why an
--emptyships nothing.
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.

