What problem does it solve? Manually updating version numbers across a .NET project risks inconsistent markers between the VERSION file, build props, and the packed MCP server manifest. This Skill automates the semver bump and proves the packed NuGet artifact carries the correct version. ## Core Features & Use Cases - Scripted Semver Bump: Run scripts/version-bump.py with patch, minor, or major to update the single hand-written VERSION file at the repo root. - Derived Version Chain: Directory.Build.props reads VERSION so assembly versions follow automatically, and a csproj target substitutes the version into the generated .mcp/server.json at pack time. - Contract Test Gate: VersionContractTests run dotnet pack and open the resulting .nupkg to verify the packed server.json carries the VERSION value. - Use Case: After merging a user-facing feature, run a minor bump, execute the VersionContractTests filter, and add a compact README "What's new" entry before shipping. ## Quick Start Bump the ai-raccoon version by one minor level and run the version contract tests to confirm the packed artifact is correct.