dotnet-release-management

Manage .NET release lifecycle with NBGV versioning and Keep a Changelog.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-release-management-rudironsoni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-release-management
Source: https://github.com/rudironsoni/dotnet-agent-harness/tree/main/.rulesync/skills/dotnet-release-management
Command: npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-release-management-rudironsoni

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 versioning consistency, accurate changelogs, and robust branching strategies.

Core Features & Use Cases

  • Automated Versioning: Leverage Nerdbank.GitVersioning (NBGV) for deterministic versioning based on Git history.
  • SemVer Compliance: Implement clear strategies for version bumping in libraries and applications.
  • Changelog Generation: Automate changelog creation using Keep a Changelog format and tools like git-cliff.
  • Release Workflows: Manage pre-release versions (alpha, beta, rc) and implement effective branching patterns (trunk-based, release branches).
  • Use Case: Ensure your open-source library follows SemVer correctly, automatically generates a CHANGELOG.md, and uses NBGV to produce unique versions for every commit.

Quick Start

Configure Nerdbank.GitVersioning for your .NET project by running nbgv install in your repository.

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 using Git history?

You can automate .NET release versioning by running `nbgv install` to configure Nerdbank.GitVersioning (NBGV), which generates deterministic versions based on your Git commit history.

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

The best way to generate a changelog for a .NET project is using the Keep a Changelog format with git-cliff, which automates changelog creation directly from your Git history.

How do I manage pre-release versions like alpha and beta in .NET?

You manage pre-release versions like alpha, beta, and rc in .NET by implementing specific release workflows and branching patterns, such as trunk-based or dedicated release branches.

Does Nerdbank.GitVersioning work with SemVer for .NET libraries?

Yes, Nerdbank.GitVersioning works with SemVer by providing clear strategies for version bumping, ensuring your .NET libraries and applications adhere to semantic versioning compliance.

When do I need a dedicated release branch for .NET versioning?

You need a dedicated release branch for .NET versioning when managing complex release lifecycles that require isolating pre-release workflows from trunk-based development.