Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Semantic Versioning 2.0.0 reference guide. Quick decision trees and examples for choosing MAJOR, MINOR, or PATCH version bumps.
Semantic Versioning 2.0.0 reference guide. Quick decision trees and examples for choosing MAJOR, MINOR, or PATCH version bumps.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Quick reference for Semantic Versioning 2.0.0 decisions.
Given version MAJOR.MINOR.PATCH, increment: LevelBump WhenReset Lower?MAJOR (X.0.0)Breaking changes (incompatible API changes)Yes, MINOR and PATCH โ 0MINOR (0.X.0)New features (backwards compatible)Yes, PATCH โ 0PATCH (0.0.X)Bug fixes (backwards compatible)No
Did you change anything users depend on? โโ No (internal only) โ PATCH โโ Yes โโ Did you remove/change existing behavior? โโ Yes โ MAJOR โโ No (only added new stuff) โโ Is the new stuff visible to users? โโ Yes โ MINOR โโ No โ PATCH
Remove a function, endpoint, or CLI flag Change the return type of a function Require a new mandatory parameter Change default behavior significantly Rename something users depend on Upgrade a dependency that forces downstream changes Examples: removeUser() โ deleteUser() rename API response format changed from {id: 1} to {data: {id: 1}} Dropping support for Node 16 (if users must upgrade)
Add new functionality Add optional parameters Add new exports/exports Deprecate old features (warn, don't remove) Performance improvements (no API change) Examples: Add createUser() alongside existing user functions Add --format json flag to CLI Add new event listeners/hooks Mark old method as deprecated (still works)
Fix bugs without changing intended behavior Documentation updates Internal refactoring (no visible change) Dependency updates (no API change) Test additions Examples: Fix null pointer exception Correct typo in error message Fix race condition Update README
ChangesVersion Bumpfix: null pointer1.2.3 โ 1.2.4feat: add auth1.2.3 โ 1.3.0breaking: remove old API1.2.3 โ 2.0.0fix: bug + feat: new thing1.2.3 โ 1.3.0 (MINOR wins)fix: bug + breaking: remove API1.2.3 โ 2.0.0 (MAJOR wins)
Use suffixes for testing before stable: 2.0.0-alpha.1 โ Very early, unstable 2.0.0-beta.2 โ Feature complete, testing 2.0.0-rc.1 โ Release candidate, final testing Pre-releases sort before their stable version: 1.0.0-alpha < 1.0.0-beta < 1.0.0-rc < 1.0.0
SituationBumpWhyFix a bug that was introduced this versionPATCHStill a fixDeprecate a feature (but keep it working)MINORNew "deprecated" state is infoChange undocumented/internal behaviorPATCHUsers shouldn't depend on itSecurity fix that requires API changeMAJORBreaking for securityRewriting internals, same behaviorPATCHInvisible to usersAdding tests/docs onlyPATCHNo code change
โ Don't bump MAJOR for big new features (unless breaking) โ Don't bump MINOR for bug fixes โ Don't bump PATCH for new functionality โ Don't keep old numbers when bumping: 1.2.3 โ 2.2.3 is wrong
Users' code breaks? โ MAJOR Users get new toys? โ MINOR Users get fixes? โ PATCH
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.