changeset-resolve
/changeset-resolve
Repair an unreleased `.changeset/*.md` file so it matches the real branch delta against `main`. Use when a changeset was edited iteratively during debugging, when bullets may reflect turn-by-turn history instead of `main...HEAD`, when "removed/gone/renamed" claims need proof, or when you need to audit whether a changeset is actually lossless before commit.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Repair an unreleased `.changeset/*.md` file so it matches the real branch delta against `main`. Use when a changeset was edited iteratively during debugging, when bullets may reflect turn-by-turn history instead of `main...HEAD`, when "removed/gone/renamed" claims need proof, or when you need to audit whether a changeset is actually lossless before commit.
Triggers from the description
Original author description
Repair an unreleased `.changeset/*.md` file so it matches the real branch delta against `main`. Use when a changeset was edited iteratively during debugging, when bullets may reflect turn-by-turn history instead of `main...HEAD`, when "removed/gone/renamed" claims need proof, or when you need to audit whether a changeset is actually lossless before commit.
How it works
- Goal
- Hard Rules
- Mandatory Sequence
- Sanity Heuristics
- Exit Gate
SKILL.md preview
---
description: Repair an unreleased `.changeset/*.md` file so it matches the real branch delta against `main`. Use when a changeset was edited iteratively during debugging, when bullets may reflect turn-by-turn history instead of `main...HEAD`, when "removed/gone/renamed" claims need proof, or when you need to audit whether a changeset is actually lossless before commit.
name: changeset-resolve
metadata:
skiller:
source: .agents/rules/changeset-resolve.mdc
---
# Changeset Resolve
Use the companion `changeset` skill for structure and versioning. This skill
owns the diff audit and the bullshit detector pass.
## Goal
Rewrite the active unreleased changeset so it describes the package-level,
user-facing branch delta against `main`, not the local iteration history.
## Hard Rules
- Diff against `main...HEAD`. Never diff against the current changeset draft.
- Reuse the existing unreleased changeset file. Do not create another one.
- Keep the release surface package-first:
- `packages/kitcn`
- `packages/resend`
- root and `example` manifests/scripts when user-facing
- docs only when they reveal public API shape
- Ignore repo noise unless it changes real user behavior:
- `.claude`
- `.agents`
- tests
- internal tooling churn
- If a bullet says something is gone, removed, renamed, or replaced, prove the
old surface existed on `main` first.
- If it did not exist on `main`, it is not a breaking change. Rewrite it as a
feature or delete it.
- Do not call a changeset lossless unless you actually audited the package
surface. If unsure, say so.
## Mandatory Sequence
1. Resolve the active changeset:
- list `.changeset/*.md` excluding `.changeset/README.md`
- reuse the existing unreleased file
2. Audit the real branch delta against `main`:
```bash
git diff --stat main...HEAD -- packages/kitcn packages/resend package.json example/package.json www/content/docs
git diff --name-only main...HEAD -- packages/kitcn packages/resend package.json example/package.json www/content/docs
git diff main...HEAD -- packages/kitcn/package.json packages/resend/package.json package.json example/package.json
```
3. Audit the likely-missed public seams:
- package `exports`
- package `bin`
- package `files`
- peer dependency/support matrix
- new packages
- public CLI commands and flags
4. Prove every breaking bullet:
```bash
git show main:packages/kitcn/package.json
git show main:packages/kitcn/src/cli/config.ts
git grep -n "claim-you-are-making" main -- packages/kitcn packages/resend www/content/docs example
```
5. Classify honestly:
- existed on `main` and changed incompatibly: `## Breaking changes`
- new user-facing capability: `## Features`
- same surface, better behavior or safer output: `## Patches`
- test-only, docs-only, or internal churn: omit
6. Rewrite from scratch:
- keep `## Breaking changes`, `## Features`, `## Patches`
- user-facing only
- no file paths
- no implementation gossip
7. Run one final anti-lie pass:
- re-check every breaking snippet against `main` and `HEAD`
- scan manifests/exports one more time
- if something still smells off, say it is not fully lossless yet
## Sanity Heuristics
- New command on this branch only: feature, not deprecation.
- New package on this branch only: feature.
- Tightened peer dependency support matrix: usually breaking.
- Moved import paths with old path removed: breaking.
- Renamed flag with old flag removed: breaking.
- Scenario/fixture proof improvements: patch only if users feel it.
- Docs sync alone: omit unless it reveals a real new surface.
## Exit Gate
Before done, run:
```bash
bun lint:fix
```
Versions
The database has no other skills named changeset-resolve.
Database snapshot: 13.11.2026 · package version b774ccde034e (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100changeset
Create a changeset for the changes in a branch. Use when: the user asks to create a changeset, add a changeset, generate a changeset, or write release notes for changed packages. - 100changeset-pr
Create or update a `.changeset/*.md` file for the current branch or PR in this repository, choose the correct package scope and release type, and verify the result against repo-specific Changesets config. Use when a publishable package changed, when a PR is missing a changeset,… - 100changeset
Create a changeset for the Astro monorepo. Use this skill whenever you need to add a changeset file to a PR, write a changelog entry, or document a package version bump. Also trigger when the user says "add a changeset", "write a changeset", "create a changeset", or when another… - 100changesets
Create or refresh a `.changeset/<slug>.md` for the current branch, or report that none is required. Triggers on "/changesets create", "add a changeset", "create a changeset", "update the changeset", "refresh the changeset", "do I need a changeset", or any work that touches… - 96changeset
Use when writing changesets for releases - 100add-changeset
Write a changeset for agentic-seo-check as a file, without the interactive prompt, in the changelog's voice. Use when a change users notice needs one, or when asked to add a changeset or a changelog entry.