dotnet-release-management

Manage .NET release lifecycle with NBGV versioning and git-cliff changelogs.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-release-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-release-management
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-release-management
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-release-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of managing the .NET release lifecycle, ensuring consistent versioning, changelog generation, and adherence to best practices.

Core Features & Use Cases

  • Automated Versioning: Integrates with Nerdbank.GitVersioning (NBGV) to deterministically calculate versions based on Git history, eliminating manual version bumps.
  • Changelog Generation: Supports Keep a Changelog format and integrates with tools like git-cliff for automatic changelog updates based on conventional commits.
  • Pre-Release & Branching Strategies: Provides clear guidance and automation for managing pre-release versions (alpha, beta, rc) and implementing effective release branching patterns (trunk-based, release branches, hotfixes).
  • Use Case: A development team can use this skill to automatically tag new releases, update version numbers in their projects, and generate a changelog entry with each commit to their main branch, significantly speeding up their release cadence.

Quick Start

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

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?

Automate .NET release versioning by integrating Nerdbank.GitVersioning (NBGV) to deterministically calculate versions based on Git history, eliminating manual version bumps and ensuring consistent SemVer strategy compliance.

What is the best way to generate a changelog for .NET projects from conventional commits?

Generate changelogs for .NET projects using git-cliff to automatically parse conventional commits and update Keep a Changelog formatted files, streamlining release notes creation for .NET 8.0+ projects.

Can I manage pre-release workflows and release branches for .NET 8.0+ projects?

Yes, you can manage pre-release workflows for alpha, beta, and rc versions alongside release branching patterns like trunk-based development and hotfixes specifically tailored for .NET 8.0+ projects.

Does Nerdbank.GitVersioning work with conventional commits for release management?

Nerdbank.GitVersioning calculates version height from Git history while conventional commits drive the changelog generation via git-cliff, together automating the entire .NET release management lifecycle.

How do I handle version height calculation and public vs. pre-release modes in .NET?

Handle version height calculation and switch between public vs. pre-release modes by configuring Nerdbank.GitVersioning (NBGV) within your .NET release branching patterns to automate versioning accurately.