What problem does it solve? Module versions determine whether consuming applications receive a change, and getting them wrong in either direction breaks distribution: too low and consumers never see the update, too high and they expect a compatibility break that never happened. This Skill governs when and how to bump a module's semantic version so changes are actually picked up. ## Core Features & Use Cases - Up-front incrementing: Move the version before implementing a change, choosing patch, minor, or major based on impact to consumers of the module's generated output. - In-flight gating: Check configured module feeds (with prereleases included) to confirm nothing at or beyond the current version is already published before bumping, avoiding phantom prerelease increments. - Dependent propagation: Update pinned dependency versions, shared-contract participants, and minimum-version floors across modules affected by the change. - Use Case: Before modifying a module's template code, run this Skill to bump its version from 1.2.0 to 1.2.1-pre.0, verify via feed search that 1.2.1 is unpublished, and update every dependent module that pins the old version. ## Quick Start Increment the version of every module this task will change, choosing the right component based on consumer impact, and confirm dependents are updated at close-out.
