dotnet-release-management

Manage .NET release lifecycle with NBGV versioning and SemVer 2.0.

71|10|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-release-management-wshaddix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-release-management
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/dotnet-release-management
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-release-management-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the complex process of managing .NET project releases, ensuring consistent versioning, accurate changelogs, and robust branching strategies.

Core Features & Use Cases

  • Automated Versioning: Leverages Nerdbank.GitVersioning (NBGV) for deterministic version calculation based on git history.
  • SemVer Compliance: Guides adherence to Semantic Versioning 2.0 for libraries and applications.
  • Changelog Generation: Facilitates the creation of clear, standardized changelogs using formats like Keep a Changelog and tools like git-cliff.
  • Release Branching: Implements effective branching patterns (Trunk-Based, Release Branches, Hotfixes) for organized development and deployment.
  • Use Case: Ensure your open-source library follows SemVer correctly, automatically generates a CHANGELOG.md from git commits, and uses NBGV to produce unique versions for every commit.

Quick Start

Use the dotnet-release-management skill to prepare for a new release by creating a release branch and updating the version.

Frequently Asked Questions about dotnet-release-management

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

FAQPage Schema
How do I automate .NET release versioning based on git history?

Automate .NET release versioning by leveraging Nerdbank.GitVersioning (NBGV) to calculate deterministic versions directly from your git history. This ensures unique versions for every commit and requires NBGV 3.6+ and .NET 8.0+ as a baseline.

What is the best way to generate a changelog from git commits for a .NET project?

Generate a .NET changelog from git commits using standardized formats like Keep a Changelog and tools such as git-cliff. This process facilitates the creation of clear, standardized changelogs to streamline your release lifecycle documentation.

How do I manage release branches and hotfixes in a .NET repository?

Manage .NET release branches and hotfixes by implementing effective git branching patterns like Trunk-Based development and dedicated Release Branches. This approach organizes development and deployment workflows for stable releases.

Does this release management approach enforce Semantic Versioning 2.0 for .NET libraries?

Yes, this release management approach guides strict adherence to Semantic Versioning 2.0 (SemVer) for both .NET libraries and applications. It covers pre-release workflows, application versioning strategies, and API compatibility validation.

Do I need NBGV to implement SemVer and release branching in .NET?

Yes, you need Nerdbank.GitVersioning (NBGV) 3.6+ and a .NET 8.0+ baseline to implement this specific release lifecycle. NBGV provides the deterministic version calculation required for strict SemVer 2.0 compliance and branching workflows.

Why should I use Nerdbank.GitVersioning over other .NET versioning tools?

Use Nerdbank.GitVersioning to achieve deterministic version calculation based on git history, ensuring consistent versioning across your .NET release lifecycle. It integrates SemVer 2.0 compliance, changelog generation, and structured release branching patterns.