agentleFS
daintreehqdaintreehq/daintree/.claude/skills/release-packages/SKILL.md

release-packages

Skill87 starsChanged 11 days agoLicence not identifiedView on GitHub

Release the plugin author npm packages (@daintreehq/plugin-sdk, @daintreehq/plugin-vite, daintree-plugin, create-daintree-plugin, @daintreehq/tour): work out which ones changed since they were last published, bump their versions with the correct cascade through dependents and the scaffold's version ranges, open the bump PR to develop, and, once main carries the bump, cut the per-package tags that make release-packages.yml publish through npm Trusted Publishing. Use this whenever the user wants to publish, release, bump, version, or ship any of the plugin packages or the plugin SDK, CLI, Vite preset or tour engine, even if they only say 'push a new SDK' or 'get the CLI fix out'. Do not use it for the Electron app release; that is the `release` skill.

  • Installs packages
  • Commits and pushes

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 4 are distinctive, and 8 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.

  • 8

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

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.