skills.rest
MudraMartin
MudraMartinCOMMUNITY
Explore all skills by this author →
GitHub

dotnet-local-tools

Manage .NET CLI tool versions across environments and CI/CD pipelines.

Updated Apr 23, 2026
Search Tags:#ci/cd#tooling#development environment#dotnet#local tools
One-click install
npx skills add https://github.com/MudraMartin/dotlight-skillset --skill dotnet-local-tools-mudramartin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-local-tools
Source: https://github.com/MudraMartin/dotlight-skillset/tree/main/dotnet/local-tools
Command: npx skills add https://github.com/MudraMartin/dotlight-skillset --skill dotnet-local-tools-mudramartin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures development teams have consistent .NET CLI tools across local environments and CI/CD pipelines, reducing conflicts and simplifying setup.

Core Features & Use Cases

  • Consistent Tooling: Centralizes tool definitions in .config/dotnet-tools.json for easy management and synchronization.
  • CI/CD Integration: Facilitates the use of the same tool versions in CI/CD pipelines, ensuring consistency.
  • Project-Specific Tools: Manages project-specific CLI tools like docfx, incrementalist, and dotnet-ef.

Quick Start

Initialize and restore local tools for your project using the dotnet-local-tools skill.

Frequently Asked Questions about dotnet-local-tools

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

FAQPage Schema
How do I maintain consistent .NET CLI tool versions across development environments?▼

Centralize your .NET CLI tool definitions in a `.config/dotnet-tools.json` file to synchronize tool versions and commands across local development environments and CI/CD pipelines. This ensures consistent and reliable .NET development workflows.

What is the best way to manage project-specific dotnet tools like dotnet-ef in CI/CD pipelines?▼

Managing project-specific dotnet tools like dotnet-ef in CI/CD pipelines is best handled by centralizing tool definitions in `.config/dotnet-tools.json`. This guarantees identical tool versions are restored and used across all pipeline runs.

Why do my .NET CLI tools have different versions between local environments and CI pipelines?▼

Different .NET CLI tool versions occur because tool definitions are not centralized. Synchronizing tool versions in a `.config/dotnet-tools.json` file ensures the same commands and versions are used across local environments and CI/CD pipelines.

Can I use a single configuration file to restore dotnet local tools across multiple environments?▼

Yes, you can use a single `.config/dotnet-tools.json` file to restore dotnet local tools. This centralizes tool management, ensuring consistent tool versions and commands are restored across multiple development environments and CI/CD pipelines.

Does dotnet-local-tools support managing project-specific CLI tools like docfx and incrementalist?▼

Yes, it supports managing project-specific CLI tools including docfx, incrementalist, and dotnet-ef. Centralizing these tool definitions ensures consistent versions and commands are used reliably across your development environments and CI/CD pipelines.

Related Skills

Explore More Software Engineering Skills→
AarononthewebAaronontheweb
1.1k

dotnet-local-tools

Manage per-repo .NET CLI tools via dotnet-tools.json manifests.

Community
Intermediate
akokenakoken
3

dotnet-local-tools

Manage local .NET CLI tools per repository using .config/dotnet-tools.json and dotnet tool restore.

Community
Intermediate
managedcodemanagedcode
4

mcaf-dotnet-format

Apply `dotnet format` to format .NET code and enforce `.editorconfig` style rules.

Official
Intermediate
rudironsonirudironsoni

dotnet-tool-management

Manage .NET CLI tools with global and local manifest installations.

Community
Intermediate