Changeset

Community

tuanductran

changeset

Use when determining whether a pull request requires a changeset, selecting the appropriate version bump (patch, minor, or major), or writing a `.changeset/*.md` entry for the hr-skills repository.

Overview

Publisher	tuanductran
Repository	`hr-skills`
Skill name	`changeset`
Stars	78
Forks	20
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 tuanductran 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/tuanductran/hr-skills/tree/main/.agents/skills/changeset
Enable the skill in any chat where you want it available.

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/tuanductran/hr-skills.git /tmp/hr-skills
mkdir -p .claude/skills
cp -r /tmp/hr-skills/.agents/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.

Changeset

Purpose

Use this skill whenever a pull request introduces user-visible changes that should be included in the next release of the hr-skills repository.

A changeset records release notes, determines semantic version bumps, and drives CHANGELOG.md generation through Changesets.

Do not create a changeset for internal-only work that has no effect on repository users.

Decision Process

Before creating a changeset, inspect the pull request and classify the changes.

A changeset is required

Create a changeset for changes such as:

New skills.
New prompts.
New examples.
New generators.
New validators.
New build capabilities.
New CLI functionality.
Bug fixes affecting repository behavior.
User-visible documentation improvements that change repository capabilities.
Any change that should appear in release notes.

A changeset is usually not required

Do not create a changeset for work such as:

Typo fixes.
Markdown formatting.
README wording improvements.
Internal refactoring.
Code movement without behavior changes.
Test-only changes.
CI configuration updates that do not affect released functionality.
Comments or cleanup work.

When uncertain, prefer consistency with previous releases and existing changesets in the repository.

Create a Changeset

Generate a new changeset:

bash
bun run changeset

Follow the interactive prompts or edit the generated file inside:

text
.changeset/

A typical file looks like:

markdown
---
"hr-skills": patch
---

Added support for validating duplicate skill names during repository validation.

Do not modify the YAML frontmatter format.

Use the exact package name defined by the repository.

Choose the Correct Version Bump

patch

Use for backward-compatible fixes and small improvements.

Examples:

Bug fixes.
Prompt improvements.
Example improvements.
Validator fixes.
Tooling corrections.
Content corrections.
Small enhancements that do not introduce new functionality.

minor

Use for new functionality that is backward compatible.

Examples:

New skill.
New prompt library.
New examples.
New validator.
New CLI command.
New build capability.
New repository feature.

major

Use for breaking changes.

Examples:

Breaking changes to SKILL.md format.
Breaking package API changes.
Folder layout changes requiring migration.
Removed repository functionality.
Incompatible validator behavior.
Repository architecture changes requiring user action.

Writing Guidelines

A good changeset explains what changed and why it matters, not how it was implemented.

General Rules

Focus on user-visible outcomes.
Write concise release notes.
Prefer one to three short sentences.
Use clear, direct language.
End every sentence with a period.
Keep descriptions suitable for inclusion in CHANGELOG.md.

Use Past Tense

Describe completed work using past tense.

Examples:

text
Added a new HR analytics skill.
Fixed duplicate validation logic.
Updated the onboarding examples.

Describe Outcomes

Prefer:

text
Added validation for duplicate skill names.

Instead of:

text
Modified validator.ts.

Release notes should describe the effect of the change, not the implementation details.

New Skills

Example:

text
Added a new `hr-virtual-onboarding` skill covering remote onboarding workflows, manager checklists, and AI-assisted onboarding prompts.

Bug Fixes

When appropriate, reference the GitHub issue.

Example:

text
Fixed #42 by correcting turnover calculation guidance in the HR analytics content.

Tooling

Example:

text
Updated repository validation to require prompts and examples for Full-tier skills.

Avoid

Do not:

Copy commit messages.
List every modified file.
Describe internal refactoring.
Include implementation details.
Repeat repository structure.
Write long release notes.
Add Markdown headings inside the description except #### or lower if absolutely necessary.

Validation Checklist

Before finishing:

Verify a changeset is actually required.
Verify the selected version bump is correct.
Verify the package name is correct.
Verify the description is concise and user-facing.
Verify Markdown formatting.
Verify the generated file is located inside .changeset/.

Do not edit generated changelog files manually.

References

AGENTS.md
README.md
docs/engineering/format.md
.changeset/
CHANGELOG.md
Changesets documentation: https://github.com/changesets/changesets/tree/main/docs
Conventional Commits: https://www.conventionalcommits.org/

Frequently asked questions

What does the Changeset AI skill do?

Use when determining whether a pull request requires a changeset, selecting the appropriate version bump (patch, minor, or major), or writing a `.changeset/*.md` entry for the hr-skills repository.

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/tuanductran/hr-skills/tree/main/.agents/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 tuanductran 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

Release Openclaw Mac

openclaw

OrganizationPopular

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

Release Openclaw Maintainer

openclaw

OrganizationPopular

Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.

Release Openclaw Plugin Testing

openclaw

OrganizationPopular

Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E,…

Solid

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Changeset

Purpose

Decision Process

A changeset is required

A changeset is usually not required

Create a Changeset

Choose the Correct Version Bump

patch

minor

major

Writing Guidelines

General Rules

Use Past Tense

Describe Outcomes

New Skills

Bug Fixes

Tooling

Avoid

Validation Checklist

References

Frequently asked questions

Related AI Skills

Set up your own AI workspace now