version-bumplisted

# Version Bump ## Core Question What version change is justified by observed evidence and project policy, and which local files must be updated consistently without tagging or publishing? ## When To Use Use this skill when the user asks to: - recommend the next version, - validate version consistency, - apply a local patch, minor, major, or prerelease bump, - update version files and lockfiles, - reason about monorepo fixed or independent versioning. ## When Not To Use Do not use this skill to create tags, publish packages, publish hosted releases, draft release notes, or edit changelog sections unless explicitly routed for evidence only. Route to: - `tag-release` for Git tag creation. - a future `publish-release` skill or manual workflow for package publication or hosted release publication. - `release-notes` for release-note text. - `changelog-maintenance` for changelog sections. - `conventional-commits` for commit classification only. ## Required Evidence Inspect or establish: - current version files such as `package.json`, `pyproject.toml`, `Cargo.toml`, `.csproj`, `VERSION`, or ecosystem equivalents, - lockfiles that must stay consistent, - release/versioning policy docs, - changelog unreleased section, - commits since last tag when recommending a bump, - conventional commit evidence when available, - breaking-change and migration evidence, - monorepo tooling and fixed/independent versioning policy, - prerelease naming and existing prerelease pattern. Do not