agentleFS
ljf06853ljf06853/keepfire/.claude/skills/release/SKILL.md

release

Skill1 starsChanged 4 months agoMITView on GitHub

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.

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

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

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Run npm run build && npm test.

    line 21
  2. Very specific:

    Commit as chore: release v<version> and tag v<version>.

    line 23
  3. Very specific:

    Do not push or npm publish unless the user explicitly asks.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 183 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

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.

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.