next-version

To safely bump a project version, this skill reads .paadhai.json, validates the new version against semver rules, requires human approval, and commits the updated config. It eliminates manual errors by ensuring the new version is greater than the current one before committing.

Semver validation works by reading the current project_version from .paadhai.json and checking that the proposed new version is valid semver and strictly greater than the existing one. The skill blocks the update and will not commit if the version is invalid or lower.

The best way to automate version bumps is running /next-version. It summarizes the version impact, waits for explicit user confirmation, updates .paadhai.json, creates a git commit, and prompts you to continue with project and release planning skills.

Yes, you need git access to update the project version. The skill requires access to git and the repository config to update .paadhai.json and create a version bump commit after receiving explicit user confirmation.

No, you cannot use this skill with any project config format. It specifically reads and updates the project_version field within the .paadhai.json config file as part of the Paadhai pipeline, and does not support other configuration formats.

The version bump process requires human approval to provide controlled execution. After displaying the current version and summarizing the impact, the skill waits for explicit confirmation before updating the config and committing, preventing unintended major version changes.