agentleFS
Sign inStart free
udecodeudecode/better-convex/.agents/skills/changeset/SKILL.md

changeset

Skill452 starsChanged 23 days agoApache-2.0View on GitHub

Use when writing changesets for releases

We split this skill into the rules it gives an agent

10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always mirror @packages/kitcn/CHANGELOG.md tone and structure.

    line 11
  2. Very specific:

    Before creating a new changeset, check .changeset/ for an existing unreleased changeset.

    line 15
  3. Distinctive:

    If one exists, UPDATE it instead of creating a new file.

    line 16
  4. Very specific:

    If a release has both breaking and non-breaking work, use minor.

    line 23
  5. Distinctive:

    Keep bullets concise and user-facing.

    line 32
  6. Very specific:

    Every breaking change must include a short Before/After code snippet immediately under that section.

    line 36
  7. Distinctive:

    If a symbol is renamed, include a dedicated rename snippet.

    line 38
  8. Very specific:

    Start bullets with action verbs: Add, Support, Fix, Improve, Deprecate, Remove, Drop.

    line 42
  9. Distinctive:

    Do not mention file paths, private implementation details, or algorithm notes.

    line 44
  10. Distinctive:

    Keep each bullet to one concrete outcome.

    line 45

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Changeset Writing

Always mirror @packages/kitcn/CHANGELOG.md tone and structure.

0) Reuse existing changeset

  • Before creating a new changeset, check .changeset/ for an existing unreleased changeset.
  • If one exists, UPDATE it instead of creating a new file. Nothing in it has been released yet, so treat it as a living draft.
  • Replace outdated content — don't append "also added..." or track progress. Write the latest state as if from scratch.

1) Versioning (project is still v0)

  • Breaking change => minor
  • Non-breaking change => patch
  • If a release has both breaking and non-breaking work, use minor.

2) Required body structure

  • Split the body into explicit sections:
    • ## Breaking changes
    • ## Features
    • ## Patches
  • Omit empty sections, but never mix categories in one section.
  • Keep bullets concise and user-facing.

3) Migration snippets (required for breaking changes)

  • Every breaking change must include a short Before/After code snippet immediately under that section.
  • Include changed imports, renamed exports, or changed call signatures.
  • If a symbol is renamed, include a dedicated rename snippet.

4) Bullet quality rules

  • Start bullets with action verbs: Add, Support, Fix, Improve, Deprecate, Remove, Drop.
  • Describe what users can do now, not internals.
  • Do not mention file paths, private implementation details, or algorithm notes.
  • Keep each bullet to one concrete outcome.

5) Copy-paste template

---
"kitcn": minor
---

## Breaking changes

- Drop ...

```ts
// Before
...

// After
...
```

## Features

- Add ...

## Patches

- Improve ...
```

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free