agentleFS
louisbrulenaudetlouisbrulenaudet/monorepo-template/.agents/skills/changeset/SKILL.md

changeset

Skill19 starsChanged 18 days agoApache-2.0View on GitHub

USE WHEN: a change under apps/ or packages/ (or an app runtime dependency bump) needs its release note, the user asks to add, fix, or check a changeset, a PR is about to open, or `pnpm release:check` fails. DO NOT USE WHEN: editing the release pipeline itself (.changeset/config.json, release.yml, the check scripts) - rule ops/release.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use better-auth-best-practices, humanizer and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • anasahmed07Skill

    better-auth-best-practices

    Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    humanizer

    Tone enforcement patterns for external-facing community responses

    Also in 5 projects that use this

  • SentrySkill

    deslop

    Strip AI-generated noise from the diff before pushing — extra comments a human wouldn't write, defensive try/catch in trusted code paths, casts to any, inline imports in Python, and other style inconsistencies with the surrounding file. Use this immediately before commit so the diff stays clean.

    Also in 3 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 3 projects that use this

  • GoogleSkill

    improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Scope: Read the branch diff (git diff origin/main...HEAD --stat, plus uncommitted work) and split it into the changes a user or operator of …

    line 10
  2. Very specific:

    never major unless the user asked for a breaking release.

    line 15
  3. Very specific:

    Use --minor in the same form, or pnpm changeset --empty -m '<one-line reason>'.

    line 27

“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, bump, and frontmatter rules live in rule ops/changesets (.claude/rules/ops/changesets.md; Cursor: .cursor/rules/ops/changesets.mdc). Read it first if it is not already loaded; this skill is only the procedure.

  1. Scope. Read the branch diff (git diff origin/main...HEAD --stat, plus uncommitted work) and split it into the changes a user or operator of a deployed app would notice. Note which apps each one reaches, including through a bundled @repo/* package or a runtime catalog bump.
  2. Reuse. git diff --name-only --diff-filter=AM origin/main -- .changeset/ lists this branch's changesets. If one already covers a change, edit it instead of adding another. If the change fixes something still pending on main, edit that pending changeset.
  3. Decide per change, with the rule's tables:
    • nothing observable ships: --empty, or no changeset at all if pnpm release:check passes without one;
    • otherwise patch or minor, naming every app whose behavior changes and never an @repo/* package;
    • never major unless the user asked for a breaking release. While the apps are 0.x, a breaking change is minor with a **Breaking:** title.
  4. Create one file per change, keeping the generated name:

    pnpm changeset --patch worker-api,front-app -m "$(cat <<'EOF'
    Imperative title of at most 100 characters naming the surface in `backticks`
    
    Optional body: operator action, changed defaults, migration.
    EOF
    )"

    Use --minor in the same form, or pnpm changeset --empty -m '<one-line reason>'.

  5. Verify. git add .changeset/<id>.md, then pnpm release:check. Fix every changesets(<rule>) line it prints and rerun until it exits 0. pnpm release:status shows the resulting versions.
  6. Report the file, the apps, and the bump in your reply and the PR description, and say why an --empty ships nothing.

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.