create-changeset
Skill30 starsChanged 16 days agoApache-2.0View on GitHub
Create or update Changesets for this repository with a Conventional Commit summary aligned verbatim to the pull request title. Use whenever asked to add, create, edit, or fix a changeset.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- techwithanirudh/coolify-tweakstheir own version, first seen Oct 8, 2026
- siemens/ixtheir own version, first seen Oct 8, 2026
- rjdellecese/confecttheir own version, first seen Oct 8, 2026
- LedgerHQ/ledger-livetheir own version, first seen Oct 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- LedgerHQ/ledger-live★ 627same name
- siemens/ix★ 390same name
- rjdellecese/confect★ 381same name
- techwithanirudh/coolify-tweaks★ 173same name
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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- create-pull-requestSkill
- e2e-testsSkill
- instrumentationSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
7
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 9
Create the changeset by writing a new Markdown file under .changeset/ directly, with a short kebab-case filename such as …
- Very specific: line 30
Use feat for a feature and fix for a bug fix.
- Very specific: line 32
Use ! immediately before the colon for a breaking change.
- Distinctive: line 34
Check whether the current branch already has a pull request with:
- Distinctive: line 40
If a pull request exists and its title is a valid, accurate Conventional Commit message, use that title verbatim as the changeset's first …
- Distinctive: line 41
If its title is not conventional or does not accurately describe the release, do not create a conflicting summary.
- Distinctive: line 43
If no pull request exists, derive one concise Conventional Commit summary from the diff.
- Distinctive: line 44
Use the exact same summary for every changeset created for the branch, and preserve it verbatim as the title when the pull request is later …
- Distinctive: line 47
Do not put introductory prose, a Markdown heading, or a list marker before the Conventional Commit summary.
- Distinctive: line 49
After creating or editing the changeset, run:
“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.
Files
Create a Changeset
Inspect the diff to identify every publishable package affected and choose the appropriate semantic version bump for each package.
Create the changeset by writing a new Markdown file under .changeset/ directly, with a short kebab-case filename such as .changeset/fix-queued-login-race.md.
---
"braintrust": patch
"@braintrust/otel": minor
---
fix: Prevent conflicting queued logins from replacing active credentialsList each affected package by its package.json name with major, minor, or patch.
Summary
The first non-empty line after the changeset frontmatter must follow Conventional Commits 1.0.0:
<type>[optional scope][optional !]: <description>Use feat for a feature and fix for a bug fix.
Other meaningful types such as docs, test, refactor, build, ci, and chore are allowed.
Use ! immediately before the colon for a breaking change.
Check whether the current branch already has a pull request with:
gh pr view --json title --jq .titleIf a pull request exists and its title is a valid, accurate Conventional Commit message, use that title verbatim as the changeset's first summary line. If its title is not conventional or does not accurately describe the release, do not create a conflicting summary; explain what needs to change before continuing.
If no pull request exists, derive one concise Conventional Commit summary from the diff. Use the exact same summary for every changeset created for the branch, and preserve it verbatim as the title when the pull request is later created.
Additional release-note detail may follow on later lines. Do not put introductory prose, a Markdown heading, or a list marker before the Conventional Commit summary.
After creating or editing the changeset, run:
node scripts/release/validate-changesets.mjsDoes 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.