agentleFS
Sign inStart free
maxwellsdm1867maxwellsdm1867/wheeler/skills/bump/SKILL.md

bump

Skill12 starsChanged 3 months agoMITView on GitHub

Use when bumping Wheeler version after shipping features. Trigger when user says 'bump version', 'release', 'cut a release', 'version bump', 'update version', or after a set of features have been committed and the user wants to formalize a new version.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use release.

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.
  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Call get_act on the wheeler_core MCP server with name="bump", then follow the returned instructions exactly.

    line 22
  2. Very specific:

    If get_act is unavailable, the Wheeler MCP servers are not connected.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 8 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
<!-- GENERATED FILE. Do not edit. Source: wheeler/_data/commands/bump.md Regenerate: python -m wheeler.build_plugin The act body is served over MCP by wheeler_core.get_act(), so it is deliberately absent here: there is exactly one copy of it. -->

Call get_act on the wheeler_core MCP server with name="bump", then follow the returned instructions exactly. They are the authoritative definition of this act. Do not improvise the workflow or substitute your own plan for it.

Pass host="codex" when running under Codex so the orchestration guidance matches the tools this host actually has.

Mode: chat. Orchestration: none.

If get_act is unavailable, the Wheeler MCP servers are not connected. Say so rather than guessing at the workflow: acting without the act text is how provenance gets silently skipped.

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