agentsclimarketplace

Version bump inference from commit subjects

Skill kjuhwa/skills-hub/skills/release/version-bump-inference-from-commit-subjects

Infer semantic version bump (major/minor/patch) from commit subjects since last releaseFrom its SKILL.md

Install
npx -y skills add kjuhwa/skills-hub --skill version-bump-inference-from-commit-subjects

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.3 KB, 208 tokens by cl100k_base, as published. Nobody here has run it

Infer semver bump from commit subjects

Parse commits since the last tag. Classify each:

  • BREAKING CHANGE: footer or trailing !: on type → major.
  • feat:minor.
  • fix: / perf:patch.
  • Default → patch.

Take the highest bump class among all commits. Works without a CHANGELOG or release history — only git log is required.

Mechanism

function bumpFor(subjects) {
  let level = 'patch';
  for (const s of subjects) {
    if (/BREAKING CHANGE/.test(s) || /!:/.test(s)) return 'major';
    if (/^feat[\(:]/i.test(s)) level = level === 'major' ? level : 'minor';
  }
  return level;
}

When to reuse

Release automation on projects that adopt Conventional Commits but don't want the full semantic-release toolchain.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.