agentsclimarketplace
Sign in

Release

Skill ljf06853/keepfire/.claude/skills/release

Cut a keepfire release — bump the version in both places it lives, build, test, commit, and tag. Use when the user asks to release, cut a version, or bump the version.From its SKILL.md

Install
npx -y skills add ljf06853/keepfire --skill release

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 381 tokens by cl100k_base, as published. Nobody here has run it

Release keepfire at version $ARGUMENTS (e.g. 0.1.2). If no version was given, ask for one; do not guess.

The version lives in four places and nothing syncs them. All must change, or keepfire --version and the plugin manifest will lie about what shipped.

  1. package.json → "version"
  2. src/cli.ts → const VERSION = "..."; (near the top of the file)
  3. .claude-plugin/plugin.json → "version"
  4. .claude-plugin/marketplace.json → plugins[0].version

Steps:

  1. Confirm the working tree is clean (git status). If not, stop and report — do not release on top of uncommitted work.
  2. Grep for the current version to be sure you catch every occurrence: search the repo for the old version string and check whether it also appears in README.md, docs/README.zh-CN.md, or agents/openai.yaml. Update any that are genuinely version claims (not changelog history or example output).
  3. Edit package.json and src/cli.ts to the new version.
  4. Run npm run build && npm test. Both must pass. If either fails, stop and report — do not tag a broken build.
  5. Smoke-check that the binary reports the new version: npm run dev -- version.
  6. Commit as chore: release v<version> and tag v<version>.
  7. Do not push or npm publish unless the user explicitly asks. Report what you did and what's left (push, tag push, publish).

Note: the npm package name is reserved but not yet published, so npm publish is not part of the routine flow.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 2 of the 12 instructions most ship operate skills give in 381 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

  • Document a rollback plan before deploymentin 41 of 779, across 22 files
  • Update the changelogin 21 of 779, across 19 files
  • Run the test suitehere, and in 20 of 779
  • Create an annotated git tagin 20 of 779
  • Clean up feature flags after full rolloutin 18 of 779, across 10 files
  • Verify deployment health after launchin 18 of 779, across 10 files
  • Test both feature flag statesin 17 of 779, across 9 files
  • Verify the working tree is cleanhere, and in 17 of 779
  • Make database migrations backward-compatiblein 16 of 779, across 8 files
  • Set up error monitoring before launchin 15 of 779, across 7 files
  • Monitor metrics at each rollout stagein 14 of 779, across 5 files
  • Create a GitHub releasein 14 of 779

Said here and by no other author read

  • update the version string everywhere
  • search the repo for the old version string
  • update genuine version claims in documentation
  • smoke-check the binary reports the new version
  • create a version tag
  • report remaining manual release steps

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,645. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.