How do I install the Dotnet CI Workflow skill?

Run npx skillmds@latest add tomevault-io/dotnet-ci-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dotnet CI Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dotnet CI Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dotnet CI Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dotnet CI Workflow?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dotnet CI Workflow by tomevault-io — Agent Skill

Name: Dotnet CI Workflow
Author: tomevault-io

File contents

Context

This project uses .NET 10, .NET Aspire (AppHost SDK via NuGet), and has the solution file at src/AvnDataGenie.sln with global.json in src/. CI workflows must account for this non-root solution layout.

Patterns

Working Directory

The solution and global.json live in src/, not the repo root. Set defaults.run.working-directory: src on the job to keep all dotnet commands scoped correctly.

Aspire AppHost in CI

The AppHost uses Aspire.AppHost.Sdk/X.Y.Z as an MSBuild SDK (resolved via NuGet). It does NOT require the deprecated Aspire workload. It compiles in CI without Docker or container runtime — it only needs containers at runtime, not build time.

NuGet Cache Key

Use hashFiles('src/**/*.csproj', 'src/global.json') to key the NuGet cache. This captures both package version changes and SDK version changes.

Action Pinning

Always pin actions to full commit SHAs with a version comment:

uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2

Concurrency

Use concurrency.cancel-in-progress: true with a branch-scoped group to avoid wasted CI minutes on rapid pushes.

Test Readiness

Wire up dotnet test even when no test projects exist. It succeeds with 0 tests and automatically picks up new test projects when added.

Anti-Patterns

Installing Aspire workload in CI — it's deprecated. The SDK resolves via NuGet.
Running CI on windows-latest without justification — doubles cost, no signal for Linux-targeted containerized apps.
Unpinned action versions — supply-chain risk. Always SHA-pin.
Missing --no-restore on build — wastes time re-resolving packages after explicit restore step.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: dotnet-ci-workflowdescription: Pattern for .NET CI pipelines with Aspire projects in GitHub Actions Use when this capability is needed.---## ContextThis project uses .NET 10, .NET Aspire (AppHost SDK via NuGet), and has the solution file at `src/AvnDataGenie.sln` with `global.json` in `src/`. CI workflows must account for this non-root solution layout.## Patterns### Working DirectoryThe solution and `global.json` live in `src/`, not the repo root. Set `defaults.run.working-directory: src` on the job to keep all `dotnet` commands scoped correctly.### Aspire AppHost in CIThe AppHost uses `Aspire.AppHost.Sdk/X.Y.Z` as an MSBuild SDK (resolved via NuGet). It does NOT require the deprecated Aspire workload. It compiles in CI without Docker or container runtime — it only needs containers at runtime, not build time.### NuGet Cache KeyUse `hashFiles('src/**/*.csproj', 'src/global.json')` to key the NuGet cache. This captures both package version changes and SDK version changes.### Action PinningAlways pin actions to full commit SHAs with a version comment:```yamluses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2```### ConcurrencyUse `concurrency.cancel-in-progress: true` with a branch-scoped group to avoid wasted CI minutes on rapid pushes.### Test ReadinessWire up `dotnet test` even when no test projects exist. It succeeds with 0 tests and automatically picks up new test projects when added.## Anti-Patterns- **Installing Aspire workload in CI** — it's deprecated. The SDK resolves via NuGet.- **Running CI on `windows-latest` without justification** — doubles cost, no signal for Linux-targeted containerized apps.- **Unpinned action versions** — supply-chain risk. Always SHA-pin.- **Missing `--no-restore` on build** — wastes time re-resolving packages after explicit restore step.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/carlfranklin) — claim your Tome and manage your conversions.

Frequently asked questions

Dotnet CI Workflow