dotnet-local-tools

Manage local .NET tools via dotnet-tools.json for reproducible builds.

57|7|Updated Aug 6, 2025

Search Tags:#ci/cd #development workflow #cli tools #.net #tool management #reproducible builds

Ready to run

npx skills add https://github.com/seiggy/lucia-dotnet --skill dotnet-local-tools-seiggy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-local-tools
Source: https://github.com/seiggy/lucia-dotnet/tree/main/.github/skills/local-tools
Command: npx skills add https://github.com/seiggy/lucia-dotnet --skill dotnet-local-tools-seiggy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all developers on a team and all CI/CD pipelines use the exact same versions of project-specific .NET CLI tools, preventing version conflicts and ensuring reproducible builds.

Core Features & Use Cases

Centralized Tool Management: Define and manage project-specific .NET tools (like DocFX, EF Core CLI, ReportGenerator) in a single dotnet-tools.json file.
Reproducible Builds: Guarantees that the same tool versions are used locally and in CI/CD environments.
Simplified CI/CD: Reduces CI setup complexity by using a single dotnet tool restore command.
Use Case: A team is using DocFX for documentation generation. By using this Skill, they can ensure everyone on the team and the CI server uses the same DocFX version, preventing documentation build failures due to version mismatches.

Quick Start

Run dotnet tool restore to install all project-specific .NET tools defined in the manifest.

Frequently Asked Questions about dotnet-local-tools

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

FAQPage Schema

How do I ensure reproducible builds with .NET CLI tools across development and CI/CD?▼

Reproducible builds are achieved by defining specific .NET tool versions in a dotnet-tools.json manifest. This guarantees local environments and CI pipelines use identical tool versions, preventing version mismatch build failures.

What is the best way to manage .NET local tools for a team project?▼

Managing .NET local tools is best handled by centralizing definitions in a dotnet-tools.json file. Teams run a single dotnet tool restore command to install the exact project-specific tool versions required for consistent execution.

How does dotnet tool restore work with a manifest file?▼

The dotnet tool restore command reads the dotnet-tools.json manifest to install the declared project-specific .NET tools. This automates setup by resolving and downloading the exact versions needed for the environment.

Can I use local .NET tools with documentation generators like DocFX?▼

Local .NET tools support documentation generators like DocFX. Defining DocFX in the dotnet-tools.json manifest ensures all team members and CI servers use the same version, preventing documentation build failures from version mismatches.

Does the dotnet-tools.json manifest work with EF Core and CSharpier?▼

The dotnet-tools.json manifest works with EF Core, CSharpier, and ReportGenerator. It tracks their specific versions to maintain consistent tooling across development environments and CI/CD pipelines.

Why do my .NET builds fail in CI due to tool version mismatches?▼

Build failures in CI from tool mismatches occur when local and server environments use different .NET tool versions. Defining project-specific tools in dotnet-tools.json prevents this by enforcing consistent versions.