skill-lorem-dev-skillkeeper-bump-version · by Install
$ agentstack add skill-lorem-dev-skillkeeper-bump-version ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-lorem-dev-skillkeeper-bump-version) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
bump-version
Bump the SkillKeeper version and prepare the release commit. Tagging and pushing remain separate, deliberate steps.
Steps
1. Require a clean working tree
Run git status --short. If there is any output, stop and ask the developer to commit or stash first. The bump must be reviewable as an isolated diff.
2. Run the bump script
Run node scripts/bump-version.mjs with the target version (for example 0.1.0-rc.1). The script:
- writes `
into the root and all workspacepackage.json` files, and - promotes
## DevelopmentinCHANGES.mdto## Version,
leaving a fresh empty ## Development block above it.
If the script exits non-zero, report the error and stop.
3. Review the diff
Run git diff and confirm the version bump touched exactly these files:
- the 3
package.jsonfiles (root,packages/i18n,apps/desktop), apps/desktop/src-tauri/tauri.conf.json(the Tauri bundle version),Cargo.toml(the workspace version every crate inherits), andCHANGES.md(the promoted## Versionsection plus a fresh empty
## Development).
No other files changed. (The old TS domain/CLI packages are gone since the Tauri migration, so there are only 3 package.json files, not the former set.)
4. Create the release commit
git add -A
git commit -m "release: "Do NOT create a tag or push. Cutting the tag is a separate, explicit step performed only after the release gate passes.
Which branch the eventual tag belongs on depends on the version you just set:
- A release candidate (
-rc.) is tagged ondevelop. It
exists to exercise the release pipeline before the work reaches the release branch, and it publishes as a GitHub pre-release, which the one-line installers ignore.
- A final release (no pre-release suffix) is tagged on
main, after
develop merges there.
scripts/check-tag-branch.mjs enforces this in the pipeline's first job, so a final tag pushed from develop fails before anything is built. Run it locally before pushing a tag to find out cheaply:
node scripts/check-tag-branch.mjs vSource & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: lorem-dev
- Source: lorem-dev/skillkeeper
- License: Apache-2.0
- Homepage: https://lorem-dev.github.io/skillkeeper/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.