dotnet-cli-release-pipeline

Automate .NET CLI tool releases via GitHub Actions with checksums and package manager updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the complex process of releasing .NET command-line interface (CLI) tools, ensuring consistent and automated delivery across multiple platforms.

Core Features & Use Cases

  • Unified Release Workflow: Manages the entire release process from a single trigger, including building, packaging, and publishing artifacts.
  • Cross-Platform Support: Builds and packages CLI tools for various Runtime Identifiers (RIDs) using a GitHub Actions matrix.
  • Automated Publishing: Creates GitHub Releases with checksums and automatically updates package manager manifests (Homebrew, winget, Scoop).
  • Use Case: When you tag a new version of your .NET CLI tool (e.g., v1.2.3), this Skill automatically builds it for Windows, macOS, and Linux, uploads the binaries to GitHub Releases, generates checksums, and submits updates to Homebrew and winget.

Quick Start

Use the dotnet-cli-release-pipeline skill to automate the release of your .NET CLI tool by pushing a git tag like 'v1.0.0'.

Frequently Asked Questions about dotnet-cli-release-pipeline

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

FAQPage Schema
How do I automate .NET CLI tool releases across multiple platforms using GitHub Actions?

Automate .NET CLI tool releases by triggering a unified GitHub Actions workflow with a git tag. This builds your tool across multiple Runtime Identifiers, stages artifacts, and creates GitHub Releases with checksums.

How do I publish .NET CLI tools to Homebrew and winget automatically?

Publish .NET CLI tools to Homebrew and winget automatically by triggering a GitHub Actions release workflow. This submits automated pull requests to update package manager manifests with your new binaries and checksums.

What is the best way to manage SemVer versioning for .NET CLI tool release pipelines?

Manage SemVer versioning for .NET CLI tool release pipelines by pushing versioned git tags like v1.2.3. This triggers the automated workflow, which handles pre-release versions and packages the binaries accordingly.

Can I build and package .NET CLI tools for Windows, macOS, and Linux in a single workflow?

Build and package .NET CLI tools for Windows, macOS, and Linux in a single workflow using a GitHub Actions matrix. This manages build configurations per Runtime Identifier (RID) and stages the resulting artifacts.

Does this release pipeline support pre-release versions for .NET CLI tools?

This release pipeline supports pre-release versions for .NET CLI tools through SemVer versioning. Tagging a pre-release version in git triggers the workflow to correctly build, package, and publish the appropriate artifacts.

How do GitHub Releases handle checksums for .NET CLI binaries?

GitHub Releases handle checksums for .NET CLI binaries by automatically generating them during the release workflow. This ensures artifact integrity when uploading cross-platform builds to the repository.