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
인공지능

widget-generator

Logo of f
f

prompts.chat 피드 시스템을 위한 사용자 지정 가능한 위젯 플러그인을 생성합니다

★ 149.6k
⑂ 0
인공지능

flags

Logo of vercel
vercel

리액트 프레임워크

★ 138.4k
⑂ 0
브라우저

pr-review

Logo of pytorch
pytorch

파이썬에서 텐서와 동적 신경망 구현 및 강력한 GPU 가속 지원

★ 98.6k
⑂ 0
개발자