changeset
Skill611 starsChanged 7 months agoMITView on GitHub
Draft a Changesets file for modified public packages in this repo.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- iangregsondev/agent-skillstheir own version, first seen Nov 16, 2026
- getlien/lientheir own version, first seen Nov 15, 2026
- venhdev/skillstheir own version, first seen Nov 8, 2026
- louisbrulenaudet/monorepo-templatetheir own version, first seen Oct 29, 2026
- frappe/frappe-uitheir own version, first seen Oct 17, 2026
- reactive/data-clienttheir own version, first seen Oct 9, 2026
Used with
Projects with it also use markdown, walkthrough and 8 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.
sarukasSkillmarkdown
Convert any document format TO Markdown. Supports 14 formats (PDF, DOCX, XLSX, PPTX, HTML, CSV, EPUB, MSG, and more) via unified CLI. Use when Claude needs to read or extract text from non-Markdown files.
Also in 3 projects that use this
MSILycanthropySkillwalkthrough
Explore and visualize codebase architecture. Use when asked to "walk me through", "show how X works", "explain the flow", "diagram the architecture", or understand how components interact.
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
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
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- 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
- deadlock-mod-manager/deadlock-mod-manager★ 617same name
- udecode/better-convex★ 453same name
- yamcodes/arkenv★ 151same name
- vobase/vobase★ 60same name
9 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.
- changesetSkill
- release-localSkill
- release-localSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Create or update a .changeset/*.md file for the current branch.
- Very specific: line 12
Only publishable packages belong in a changeset: @openharness/core, @openharness/react, @openharness/vue, @openharness/provider-vfs.
- Distinctive: line 14
If the branch only changes docs, examples, or website content, say that no changeset is needed instead of inventing one.
- Very specific: line 15
Prefer the smallest valid bump.
- Distinctive: line 16
Write notes for users, not implementation archaeology.
- Very specific: line 22
If the bump is ambiguous, or if any package needs a major bump, stop and ask for confirmation before writing the file.
- Very specific: line 23
Write the changeset file in .changeset/ with frontmatter for the affected packages and a concise note below it.
- Distinctive: line 26
If the user supplied extra context in the command arguments, incorporate it into the summary when it improves the release note.
“Common” is measured: kept by at least 6 in 10 of the 16 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
Create or update a .changeset/*.md file for the current branch.
Repo-specific rules:
- Only publishable packages belong in a changeset:
@openharness/core,@openharness/react,@openharness/vue,@openharness/provider-vfs. - Ignore
apps/*andexamples/*unless they reveal a user-facing package behavior change that should still be described under one of the public packages. - If the branch only changes docs, examples, or website content, say that no changeset is needed instead of inventing one.
- Prefer the smallest valid bump. Use
majoronly for real breaking API or behavior changes. - Write notes for users, not implementation archaeology. One short paragraph is usually enough.
Workflow:
- Inspect staged changes first. If nothing is staged, compare the branch against
main. - Identify which public packages changed and choose the bump level for each package.
- If the bump is ambiguous, or if any package needs a
majorbump, stop and ask for confirmation before writing the file. - Write the changeset file in
.changeset/with frontmatter for the affected packages and a concise note below it. - Show the file contents after writing it.
If the user supplied extra context in the command arguments, incorporate it into the summary when it improves the release note.
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.

