# Changeset

> Create a changeset from git history for the current branch. Use when the user asks to create a changeset, prepare a release, or generate a changeset from commits. Use when this capability is needed.

- Skill: `tomevault-io/changeset-4` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/changeset-4`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/changeset-4/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/changeset-4

---


# Create Changeset from Git History

Create a changeset for the current branch automatically:

1. Gather all changes:
   - Run `git log main..HEAD --oneline` to get all commits on this branch
   - Run `git diff` to see unstaged changes
   - Run `git diff --cached` to see staged changes
2. Analyze the commits and current changes to determine the semver bump:
   - `major` if any commit contains "BREAKING" or "!"
   - `minor` if any commit starts with "feat"
   - `patch` otherwise (fix, chore, refactor, docs, etc.)
3. Generate a concise summary (1-2 sentences) describing all changes (commits + uncommitted)
4. Create a changeset file by running `bunx changeset add --empty` then editing the created file, OR by directly writing a new file to `.changeset/` with a random kebab-case name (e.g., `tall-lions.md`)

The changeset file format:

```markdown
---
'cli-lsp-client': <patch|minor|major>
---

<your generated summary>
```

Do not ask any questions - determine everything from the git history and create the changeset file directly.

---
> Source: [eli0shin/cli-lsp-client](https://github.com/eli0shin/cli-lsp-client) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-22 -->