agentleFS
MaxGfellerMaxGfeller/open-harness/.claude/skills/changeset/SKILL.md

changeset

Skill611 starsChanged 7 months agoMITView on GitHub

Draft a Changesets file for modified public packages in this repo.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use markdown, walkthrough and 8 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.
  • sarukasSkill

    markdown

    Convert any document format TO Markdown. Supports 14 formats (PDF, DOCX, XLSX, PPTX, HTML, CSV, EPUB, MSG, and more) via unified CLI. Use when Claude needs to read or extract text from non-Markdown files.

    Also in 3 projects that use this

  • MSILycanthropySkill

    walkthrough

    Explore and visualize codebase architecture. Use when asked to "walk me through", "show how X works", "explain the flow", "diagram the architecture", or understand how components interact.

    Also in 3 projects that use this

  • VercelSkill

    turborepo

    Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries.

    Also in 3 projects that use this

  • 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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Create or update a .changeset/*.md file for the current branch.

    line 8
  2. Very specific:

    Only publishable packages belong in a changeset: @openharness/core, @openharness/react, @openharness/vue, @openharness/provider-vfs.

    line 12
  3. Distinctive:

    If the branch only changes docs, examples, or website content, say that no changeset is needed instead of inventing one.

    line 14
  4. Very specific:

    Prefer the smallest valid bump.

    line 15
  5. Distinctive:

    Write notes for users, not implementation archaeology.

    line 16
  6. Very specific:

    If the bump is ambiguous, or if any package needs a major bump, stop and ask for confirmation before writing the file.

    line 22
  7. Very specific:

    Write the changeset file in .changeset/ with frontmatter for the affected packages and a concise note below it.

    line 23
  8. Distinctive:

    If the user supplied extra context in the command arguments, incorporate it into the summary when it improves the release note.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 16 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

Create or update a .changeset/*.md file for the current branch.

Repo-specific rules:

  • Only publishable packages belong in a changeset: @openharness/core, @openharness/react, @openharness/vue, @openharness/provider-vfs.
  • Ignore apps/* and examples/* unless they reveal a user-facing package behavior change that should still be described under one of the public packages.
  • If the branch only changes docs, examples, or website content, say that no changeset is needed instead of inventing one.
  • Prefer the smallest valid bump. Use major only for real breaking API or behavior changes.
  • Write notes for users, not implementation archaeology. One short paragraph is usually enough.

Workflow:

  1. Inspect staged changes first. If nothing is staged, compare the branch against main.
  2. Identify which public packages changed and choose the bump level for each package.
  3. If the bump is ambiguous, or if any package needs a major bump, stop and ask for confirmation before writing the file.
  4. Write the changeset file in .changeset/ with frontmatter for the affected packages and a concise note below it.
  5. Show the file contents after writing it.

If the user supplied extra context in the command arguments, incorporate it into the summary when it improves the release note.

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.