Version bump inference from commit subjects
Skill kjuhwa/skills-hub/skills/release/version-bump-inference-from-commit-subjects
Self-correcting knowledge corpus for Claude Code — 9 stable shape clusters, bias-correction pipeline baked into contribution flow. 47 papers, 45 techniques, 1.1k skills.
npx -y skills add kjuhwa/skills-hub --skill version-bump-inference-from-commit-subjectsAssembled 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.
What its author says it does
Copied from the file, not written here
Infer semantic version bump (major/minor/patch) from commit subjects since last release
SKILL.md
1.3 KB, 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.