agentleFS
Sign inStart free
ShipfoxHQShipfoxHQ/shipfox/.agents/skills/generate-changeset/SKILL.md

generate-changeset

Skill87 starsChanged 12 days agoMITView on GitHub

Generate a Changeset file for the current branch using Shipfox agent automation. Trigger when the user asks to add a Changeset, document a change for release, bump versions, or prepare a PR that touches published packages.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. tabler/tabler★ 42ksame name
    2. GabeDuarteM/blocky-ui★ 132same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When a change may affect a published package, read the Changesets and publishing workflow.

    line 12
  2. Distinctive:

    Before writing the summary, read the repository writing guide.

    line 17
  3. Distinctive:

    Write the summary using the shared workflow.

    line 31
  4. Distinctive:

    Use one front-matter entry per affected package.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Generate Changeset

Agents cannot drive the interactive pnpm exec changeset prompt. This skill creates the equivalent .changeset/*.md file directly.

When a change may affect a published package, read the Changesets and publishing workflow. It owns when a Changeset is required, package eligibility, bump levels, and the shared summary rules.

Before writing the summary, read the repository writing guide. Apply its word, terminology, contraction, and sentence-length rules. Changeset summaries are published as release notes and are checked by the prose policy.

Process

  1. Inspect git diff origin/main...HEAD --name-only and apply the shared workflow to decide whether a Changeset is required.
  2. For each changed package, walk upward to its nearest package.json. Read its name and private fields. Include only eligible published packages.
  3. Apply the shared bump-level policy. If the change is breaking, explain the major-version impact and ask the user before writing it.
  4. Generate an unused three-word filename under .changeset/ and write the standard Changesets front matter with the selected package names and bumps.
  5. Write the summary using the shared workflow. Do not create a release pull request or run the publisher.
  6. Report the filename, package bumps, and summary. The calling workflow is responsible for committing the file with the implementation.

File shape

---
"@shipfox/api-runners": minor
---

Adds per-organization runner concurrency limits.

Use one front-matter entry per affected package.

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