Analyze current project changes, propose a short Russian commit message, and choose the correct semver bump for `package.json`. Use when the user asks to prepare a commit, determine PATCH/MINOR/MAJOR, bump the project version before a release, or summarize staged/unstaged changes into commit metadata.
Inspect the current project changes, decide the semver bump, update only package.json.version, and return a compact result the user can use for a commit.
Prefer PATCH when the change type is ambiguous.
Inspect the current changes.
Use git status --short and a focused diff summary to understand the main change.
Read the current version from package.json.
Update only the version field. Do not change other fields while applying the version bump.
Classify the bump strictly by semver.
MAJOR: any breaking changeMINOR: new functionality without breaking changesPATCH: bug fixes, minor refactors, small improvements without new functionalityPATCHWrite a short Russian commit message. Reflect the main user-visible or engineering-relevant change. Keep it compact and specific.
Return the result in the required format. Always use:
Коммит: ...
Версия: old -> new
package.json is missing or has no version, state the blocker clearly instead of inventing a value.Коммит: Исправить потерю первого клика при голосовании
Версия: 1.6.0 -> 1.6.1