semantic-versioning

To automatically determine the correct SemVer bump from code changes, the Skill analyzes your modifications and commit conventions to map the change to a MAJOR, MINOR, or PATCH bump. It then reads the current version from your project manifest and applies the increment.

You can apply a version bump to package.json or Cargo.toml without a separate commit by integrating the version increment directly into your current code change commit. The Skill updates the manifest and records the bump in the same commit message.

You need a MINOR versus a PATCH version bump when your code changes introduce new backward-compatible functionality rather than a backward-compatible bug fix. The Skill identifies the change type based on your project conventions and maps it to the correct semantic versioning increment.

Yes, this semantic versioning approach works with both Rust and Node.js project manifests. The Skill reads the current version directly from project manifests such as Cargo.toml or package.json and applies the corresponding version increment.

The best way to keep a project's version aligned with code changes is to evaluate modifications after they are made and automatically apply the correct semantic version increment. This ensures the manifest version accurately reflects the nature of the code changes without requiring manual tracking.

A limitation of mapping code changes to semantic versioning automatically is that the accuracy of the MAJOR, MINOR, or PATCH bump depends heavily on your project's commit conventions. The Skill requires a clear manifest like Cargo.toml or package.json to read and update the current version.