version-bump

Bump Version or VersionPrefix properties across solution projects after confirmation.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill version-bump-darylmcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-bump
Source: https://github.com/darylmcd/Roslyn-Backed-MCP/tree/main/skills/version-bump
Command: npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill version-bump-darylmcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates bumping Version/VersionPrefix properties across all projects in a loaded solution, ensuring consistent version numbers during releases.

Core Features & Use Cases

  • Discover all projects with Version or VersionPrefix properties by evaluating MSBuild props.
  • Compute the new version per project based on patch, minor, or major bumps.
  • Preview changes per project and apply them atomically after explicit confirmation, then verify the solution compiles.

Quick Start

Provide a bump type (patch, minor, or major) and run the skill to perform the version bump across the loaded solution.

Frequently Asked Questions about version-bump

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bump versions across all projects in an MSBuild solution at once?

Bumping versions across all projects in an MSBuild solution at once is done by calculating a new semantic version and applying it to Version or VersionPrefix properties across the loaded solution atomically after user confirmation.

How does semantic versioning work when updating multiple project files?

Semantic versioning calculates the new version based on a specified bump type—patch, minor, or major. It evaluates MSBuild properties to locate version fields per project, previews the changes, and applies the mutations atomically.

Can I preview version property changes before they are applied to my solution?

Yes, you can preview version property changes before they are applied. The process computes the new version per project and presents a preview of all pending changes, applying the mutations only after you provide explicit confirmation.

Do I need Roslyn to evaluate MSBuild props for a version bump?

Yes, you need Roslyn for property evaluation and MSBuild project graph access. It is used to locate and evaluate Version or VersionPrefix properties across all projects in the loaded solution before mutating them.

What is the best way to ensure consistent version numbers during a multi-project release?

The best way to ensure consistent version numbers during a multi-project release is to automate bumping Version or VersionPrefix properties across all projects in a loaded solution atomically, verifying the solution compiles after applying the changes.

What happens if a version bump causes my solution to fail compilation?

After applying version mutations atomically, the skill verifies that the solution compiles. This ensures that any issues introduced during the version bump process are immediately caught after the changes are applied.