changeset — editor changeset, community, editor, ide skills, headless, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

このスキルについて

開発エージェントが自動化されたパッケージ管理と効率的なコミット分析を必要とする場合に最適です。 Create a changeset for package releases. Analyzes commits since the last release, determines affected packages and bump type, and generates a changeset file.

# Core Topics

editor headless
vimeejs vimeejs
[18]
[0]
Updated: 3/24/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
7/11
Quality Score
36
Canonical Locale
en
Detected Body Locale
en

開発エージェントが自動化されたパッケージ管理と効率的なコミット分析を必要とする場合に最適です。 Create a changeset for package releases. Analyzes commits since the last release, determines affected packages and bump type, and generates a changeset file.

このスキルを使用する理由

エージェントが最後のリリースタグ以降のコミットを分析し、Git タグとバージョン管理を使用して効率的なパッケージ管理のための変更セットを作成できるようにし、ワークフローを自動化し、AI コーディング アシスタント（Claude Code など）で生産性を向上させます。

おすすめ

開発エージェントが自動化されたパッケージ管理と効率的なコミット分析を必要とする場合に最適です。

↓ 実現可能なユースケース for changeset

パッケージ更新の変更セットの自動作成
最後のリリースタグ以降のコミットを分析して効率的なパッケージ管理を実現
自動化されたワークフローと AI コーディング アシスタントで開発者の生産性を向上させる

! セキュリティと制限

  • Git バージョン管理システムが必要
  • パッケージ リリース タグへのアクセスが必要
  • パッケージ リリース タグの形式が '@vimee/<name>@<version>' のパッケージのみに限定

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is changeset?

開発エージェントが自動化されたパッケージ管理と効率的なコミット分析を必要とする場合に最適です。 Create a changeset for package releases. Analyzes commits since the last release, determines affected packages and bump type, and generates a changeset file.

How do I install changeset?

Run the command: npx killer-skills add vimeejs/vimee/changeset. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for changeset?

Key use cases include: パッケージ更新の変更セットの自動作成, 最後のリリースタグ以降のコミットを分析して効率的なパッケージ管理を実現, 自動化されたワークフローと AI コーディング アシスタントで開発者の生産性を向上させる.

Which IDEs are compatible with changeset?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for changeset?

Git バージョン管理システムが必要. パッケージ リリース タグへのアクセスが必要. パッケージ リリース タグの形式が '@vimee/<name>@<version>' のパッケージのみに限定.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add vimeejs/vimee/changeset. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use changeset immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Imported Repository Instructions

The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.

Supporting Evidence

changeset

Install changeset, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly
Imported Repository Instructions
The section below is supporting source material from the upstream repository. Use the Killer-Skills review above as the primary decision layer.
Supporting Evidence

Changeset Skill

Create a changeset by analyzing commits since the last release tag.

Workflow

1. Identify the last release tag for each package

List all release tags sorted by version:

bash
1git tag --list '@vimee/*' --sort=-version:refname

From this output, extract the latest (highest version) tag for each package name. Tags follow the format @vimee/<name>@<version>. For each unique package name, take the first (highest) tag.

2. Determine affected packages per-package

For each package, use its latest tag from step 1 to compare against HEAD. Only check src/ directories to focus on source changes:

bash
1# For each package, substitute <LATEST_TAG> with the actual latest tag found in step 1.
2# Example: if the latest tag for core is @vimee/core@0.3.0, run:
3#   git log '@vimee/core@0.3.0..HEAD' --oneline -- packages/core/src
4git log '<LATEST_TAG>..HEAD' --oneline -- packages/<name>/src

Do this for every package that has at least one release tag. If a package has no release tag yet, skip it or ask the user.

Only include packages that have actual source changes (ignore CI-only or docs-only changes outside packages/*/src).

3. Determine bump type for each package

Analyze the commit messages for each affected package:

Commit prefixBump type
fix:patch
feat:minor
BREAKING CHANGE or !: in messagemajor
chore:, ci:, docs:, refactor:, test:No bump needed (skip unless they contain functional changes)

Choose the highest bump type found across all commits for each package.

If the bump type is ambiguous or could be interpreted as either minor or major, ask the user before proceeding.

4. Confirm with user

Present the plan before creating the changeset, showing per-package comparisons:

<package> (since <its-latest-tag>):
- <commit list for that package>

Changeset:
- @vimee/<pkg>: <bump>
  ...

Summary: <one-line description>

Ask: "Does this look right?" — adjust if the user wants to change the bump type or summary.

5. Create the changeset file

Write to .changeset/<descriptive-name>.md:

markdown
1---
2"@vimee/shiki-editor": patch
3"@vimee/core": minor
4---
5
6<summary describing what changed and why>

6. Commit the changeset

Commit with message: chore: add changeset for <brief description>

Important Notes

  • Do NOT run changeset version or changeset publish — the release.yaml GitHub Action handles versioning and publishing automatically when changesets are merged to main.
  • updateInternalDependencies is set to "patch" in .changeset/config.json, so dependents get bumped automatically.
  • If there are no package changes since the last tag (only CI/docs changes), inform the user that no changeset is needed.

関連スキル

Looking for an alternative to changeset or another community skill for your workflow? Explore these related open-source skills.

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

React フレームワーク

★ 138.4k
⑂ 0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク（強力なGPUアクセラレーション）

★ 98.6k
⑂ 0
開発者