agentleFS
Sign inStart free
GabeDuarteMGabeDuarteM/blocky-ui/.agents/skills/generate-changeset/SKILL.md

generate-changeset

Skill132 starsChanged 2 months agoMITView on GitHub

Changesets for blocky-ui. Use when the user requests a changeset or release-note draft for repository changes.

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. ShipfoxHQ/shipfox★ 87same 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 repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read .changeset/README.md, .changeset/config.json, and package.json.

    line 8
  2. Distinctive:

    Use a comparable consumed changeset's final revision before deletion for wording and level of detail.

    line 11
  3. Distinctive:

    Check the completed entries against the requested changes and README.

    line 17
  4. Very specific:

    When in doubt between patch and minor, choose based on user-visible capability: fixes and optimizations are patch.

    line 29

≈ “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

  1. Read .changeset/README.md, .changeset/config.json, and package.json. Compare the requested changes with pending changesets so each user-facing change is covered once.
  2. Use a comparable consumed changeset's final revision before deletion for wording and level of detail. The README takes precedence over historical formatting.
  3. For uncovered changes, create files with bun run changeset --empty. Apply the bump policy below and the README's format. Multiple changesets per PR are valid: split independent user-facing changes or different bump types; keep related implementation details together.
  4. Check the completed entries against the requested changes and README. Report the files and their bumps, or existing coverage if no new entry was needed.

Bump policy

  • patch: bug fixes, dependency/CVE bumps, docs/config clarifications, and performance improvements that do not add a user-facing capability.
  • minor: new provider support, new configuration options, new filters, new dashboard sections, or any meaningful new feature.
  • major: breaking configuration changes, removed compatibility, migrations users must perform immediately, or behavior that breaks existing setups.

When in doubt between patch and minor, choose based on user-visible capability: fixes and optimizations are patch; new features and supported integrations are minor.

Writing reference

  • Include tables only when comparing measurable before/after results.
  • For visual changes, include screenshots using supplied GitHub attachment or Imgur URLs. When screenshots are missing, use clearly labeled temporary placeholders from https://placehold.co/ and report this to the user.

For a requested dry-run, follow the README's preview instructions.

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