Changeset

Organization

modem-dev

changeset

Use this skill when a Biome change may affect users and you must decide whether it needs a changeset, choose the release level, or create and edit `.changeset/*.md` release-note text. Do not use for implementation details or PR descriptions.

Overview

Publisher	modem-dev
Repository	`ossrules`
Skill name	`changeset`
Stars	65
Forks	2
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by modem-dev on GitHub. Read the source before you install it.

Installation

Install the Changeset AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/modem-dev/ossrules/tree/main/public/files/biomejs/.claude/skills/changeset
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/modem-dev/ossrules/tree/main/public/files/biomejs/.claude/skills/changeset

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/modem-dev/ossrules.git /tmp/ossrules
mkdir -p .claude/skills
cp -r /tmp/ossrules/public/files/biomejs/.claude/skills/changeset .claude/skills/changeset

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Changeset in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Changeset on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Changeset is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Changesets

Changesets describe user-visible behavior for release notes. Root AGENTS.md defines when automated contributions require one; CONTRIBUTING.md is canonical for package selection, versioning, branch targets, and prose format.

Decide Whether One Is Required

A changeset is required for behavior visible to users of the CLI, libraries, published crates, diagnostics, parser, formatter, linter, or assists.

No changeset is needed for an internal refactor with identical behavior, tests only, CI/build maintenance, or documentation-only edits.

Before opening a PR, explicitly confirm the user-facing classification as required by AGENTS.md. Do not infer user visibility only from the files changed.

Choose the Release Level

Change	Level	Target
Bug fix or non-breaking behavior correction	`patch`	`main`
New nursery lint rule	`patch`	`main`
New user-facing feature or nursery promotion	`minor`	`next`
Breaking user API change	`major`	`next`

Nursery rules are the exception to the usual new-feature mapping because they do not follow semantic versioning. Verify unusual cases against the current versioning policy.

Create the File

Run just new-changeset-empty to generate an empty file.

shell
just new-changeset-empty

An empty generated entry starts with frontmatter delimiters. Replace that frontmatter with the package and release level rather than appending a second block:

markdown
---
"@biomejs/biome": patch
---

Description.

Use #### or ##### for headings inside a longer entry. Other heading levels interfere with changelog generation.

Write the Entry

Describe user-visible behavior, not implementation.
Use one to three sentences unless the impact genuinely needs an example.
Use past tense for the contribution and present tense for resulting Biome behavior.
Start bug fixes with the linked issue when one exists.
Link rule and assist names to their Biome website pages.
End every sentence with a full stop.

Include only the example needed to understand impact:

new rule: an invalid example;
existing rule: what became valid or invalid;
formatter: a diff block;
parser: source that now parses or is now rejected.

Do not copy a PR summary into the changeset. A changeset is release-note text and should omit test plans, internal design, and reviewer guidance.

Review Checklist

The behavior is user-visible.
The package is correct.
The release level agrees with branch policy.
The description matches the implemented behavior.
Issue, rule, and assist links are accurate.
Examples show observable impact.
The file has one valid frontmatter block.

References

Changeset policy: CONTRIBUTING.md#changelog
Branch targeting: CONTRIBUTING.md#creating-pull-requests
Versioning: https://biomejs.dev/internals/versioning/
Generator recipes: justfile

Frequently asked questions

What does the Changeset AI skill do?

Why use Changeset on TypingMind?

Because you install it once and use it with any model. Changeset is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Changeset in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/modem-dev/ossrules/tree/main/public/files/biomejs/.claude/skills/changeset. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Changeset?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Changeset?

As many as you like. As long as a model supports skills, you can use Changeset with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Changeset AI skill free?

Yes. It is published on GitHub by modem-dev under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Refactor Docs

openclaw

OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

Openclaw Repair Sweep

openclaw

OrganizationPopular

Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

Openclaw Test Performance

openclaw

OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

Openclaw Testing

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Changesets

Decide Whether One Is Required

Choose the Release Level

Create the File

Write the Entry

Review Checklist

References

Frequently asked questions

Related AI Skills

Set up your own AI workspace now