dotnet-local-tools

Manage per-repository .NET CLI tools with dotnet-tools.json manifests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tvcosta/ai-customer-service --skill dotnet-local-tools-tvcosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-local-tools
Source: https://github.com/tvcosta/ai-customer-service/tree/main/.claude/skills/local-tools
Command: npx skills add https://github.com/tvcosta/ai-customer-service --skill dotnet-local-tools-tvcosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing local .NET tools with dotnet-tools.json for consistent tooling across development environments and CI/CD pipelines.

Core Features & Use Cases

  • Local tools are installed per-repository and restored with dotnet tool restore to avoid global conflicts.
  • Pin specific tool versions in .config/dotnet-tools.json to ensure reproducible builds across environments.
  • Supports common .NET CLI tools (docfx, dotnet-ef, incrementalist, etc.) and smooth CI integration.

Quick Start

Initialize the manifest with dotnet new tool-manifest, install required tools locally, and restore them in CI.

Frequently Asked Questions about dotnet-local-tools

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

FAQPage Schema
How do I manage .NET CLI tools consistently across local development and CI pipelines?

Managing .NET CLI tools consistently across local development and CI requires a per-repository tool manifest at .config/dotnet-tools.json. You initialize it with dotnet new tool-manifest, install required tools locally, and restore them in CI using dotnet tool restore to ensure reproducible builds.

What is the purpose of a dotnet tool manifest?

A dotnet tool manifest is a per-repository configuration file that pins specific .NET CLI tool versions. It ensures reproducible tooling across environments by isolating tools from global installations and allowing CI pipelines to restore exact versions using dotnet tool restore.

How do I pin specific versions of dotnet-ef and docfx for my repository?

To pin specific versions of dotnet-ef and docfx, you install them locally into a tool manifest using dotnet tool install. This records the exact versions in .config/dotnet-tools.json, which can then be restored consistently across development and CI environments.

Can I isolate .NET local tools from global installations to prevent version conflicts?

Yes, .NET local tools are isolated from global installations by design. They are installed per-repository using a tool manifest at .config/dotnet-tools.json and restored locally with dotnet tool restore, preventing version conflicts across different projects and environments.

Does dotnet tool restore work with CI pipelines for reproducible builds?

Yes, dotnet tool restore works seamlessly with CI pipelines to ensure reproducible builds. By reading the .config/dotnet-tools.json manifest, the command automatically installs the exact pinned versions of required .NET CLI tools during the CI setup phase.

What is the best way to share dotnet-tools configuration across a development team?

The best way to share dotnet-tools configuration across a team is committing the .config/dotnet-tools.json manifest to your repository. Team members and CI pipelines then run dotnet tool restore to automatically install the matching tool versions locally.