agentleFS
Sign inStart free
feichai0017feichai0017/QuillSQL/.agents/skills/version-bump/SKILL.md

version-bump

Skill337 starsChanged 18 days agoApache-2.0View on GitHub

Update OrbitKV package versions or prepare a release candidate while keeping Rust, Python, CUDA distributions and release tags consistent.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 1

    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:

    Read AGENTS.md and docs/releases.md from the Git root.

    line 8
  2. Very specific:

    Run python3 scripts/check-versions.py --tag vVERSION.

    line 16
  3. Distinctive:

    Keep artifacts and qualification results outside Git.

    line 24

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

OrbitKV versions and release candidates

Read AGENTS.md and docs/releases.md from the Git root. Follow the user's requested version and release scope; candidate preparation and publishing are different operations. Existing session authorization still applies.

  1. Inspect the current version, working tree and branch. Update Cargo.toml [workspace.package], python/pyproject.toml [project] and [tool.commitizen] together. Refresh affected workspace entries in Cargo.lock without upgrading unrelated dependencies.
  2. Run python3 scripts/check-versions.py --tag vVERSION. Both orbitkv-llm and orbitkv-llm-cu13 must have the same version and retain their documented engine/runtime constraints. Check the release matrix in docs/completion-plan.md; an engine target becomes supported only after its upgrade gate passes. Keep license and bundled upstream provenance with artifacts.
  3. Build the candidate with scripts/build-wheel.sh or the manual Release workflow. Check the complete installed package, Manager and loaded TENT paths, then execute the relevant installed-engine and two-host gates.
  4. Keep artifacts and qualification results outside Git. Supply their version, source commit, hashes, reproduction commands and known limits for review.

A matching v* tag triggers GitHub/PyPI publication in this repository; do not push one merely to test version consistency. Publish only within the user's release authorization and after candidate acceptance. Do not embed credentials or replace the project's release workflow with skill-specific scripts.

Download now (ZIP)

  • Other versions23 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 23

    1. meteor/meteor★ 45ksame name
    2. BenedictKing/ccx★ 4ksame name
    3. marketcalls/openalgo★ 2.9ksame name
    4. swoosh/swoosh★ 1.5ksame name
    5. microsoft/roosterjs★ 1.3ksame name
    6. Kindness-Kismet/Storage-redirection-X-Public★ 498same name
    7. deadlock-mod-manager/deadlock-mod-manager★ 489same name
    8. Kindness-Kismet/One-Player★ 463same name
    9. novitalabs/pegaflow★ 214same name
    10. nerdai/llm-agents-from-scratch★ 192same name

    13 more not listed

    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.

  • Used alongsideProjects with it also use babysit.

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

      babysit

      Use when an authorized pull request needs ongoing CI and review follow-through.

      Also in 3 projects that use this

  • In this repository4 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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