dotnet-github-actions

Generate standardized GitHub Actions CI/CD workflows for .NET repositories.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/afonsoft/gamehub --skill dotnet-github-actions-afonsoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-github-actions
Source: https://github.com/afonsoft/gamehub/tree/main/.claude/skills/dotnet-github-actions
Command: npx skills add https://github.com/afonsoft/gamehub --skill dotnet-github-actions-afonsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up consistent CI/CD, security scanning, code quality, and NuGet publishing workflows across multiple .NET repositories is repetitive and error-prone, with each repo needing different triggers, secrets, and build steps. ## Core Features & Use Cases - Workflow Templates: Provides ready-to-copy templates for CI build/test, code quality (Qodana, SonarQube, Snyk), security scanning (CodeQL), NuGet publishing, release pipelines, and artifact cleanup. - Repository Archetype Matching: Maps repos to archetypes (.NET class library, ABP/EAF web + Angular, multi-target with native dependencies) and selects the right template set. - Standardized Conventions: Enforces pinned action versions, required secrets, branch trigger patterns, and env variable placeholders across all workflows. - Use Case: When bootstrapping a new .NET NuGet library, copy the ci-dotnet-library, code-quality, security-scan, and publish-nuget templates, replace the SOLUTION_FILE placeholder, and get a full pipeline with coverage artifacts and dual NuGet.org/GitHub Packages publishing. ## Quick Start Ask the assistant to generate GitHub Actions workflows for your .NET repository using this skill, providing your solution file name and branching model.

Frequently Asked Questions about dotnet-github-actions

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

FAQPage Schema
How do I set up GitHub Actions CI for a .NET library?▼

Copy the ci-dotnet-library.yml template into .github/workflows and replace the SOLUTION_FILE placeholder with your .sln path. It builds, tests with coverage, and uploads artifacts on pushes to feature branches and PRs to main.

How to publish NuGet packages with GitHub Actions?▼

Use the publish-nuget.yml template, which packs your solution and pushes to both GitHub Packages and NuGet.org on version tags or releases. It requires a NUGET_TOKEN secret for NuGet.org and uses GITHUB_TOKEN for GitHub Packages.

Does this support .NET projects with Angular frontends?▼

Yes, the ci-dotnet-web-angular.yml template handles ABP/EAF-style repos with separate backend and frontend jobs. It builds the .NET API solution and runs npm ci, lint, build, and tests in the Angular working directory.

What secrets are required for the security scanning workflow?▼

The security-scan.yml workflow uses CodeQL with no extra secrets, while Snyk requires SNYK_TOKEN and SonarQube requires SONAR_TOKEN. Both Snyk and SonarQube steps skip gracefully if their tokens are not configured.

Why does the SonarQube job not run on pull requests?▼

The SonarQube job is gated to run only on push and workflow_dispatch events, matching SonarCloud conventions where PR analysis is handled separately. The security-scan template also disables it by default when SonarCloud automatic analysis is enabled.