skills.rest
tientt010
tientt010COMMUNITY
Explore all skills by this author →
GitHub

dotnet-local-tools

Manage per-repository .NET tool manifests with dotnet tool restore.

Updated Feb 10, 2026
Search Tags:#dotnet#ci-cd#tool-manifest#local-tools#reproducible-builds#project-tooling
One-click install
npx skills add https://github.com/tientt010/Dotnet-JiraLite-Microservices --skill dotnet-local-tools-tientt010
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-local-tools
Source: https://github.com/tientt010/Dotnet-JiraLite-Microservices/tree/main/.github/skills/local-tools
Command: npx skills add https://github.com/tientt010/Dotnet-JiraLite-Microservices --skill dotnet-local-tools-tientt010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardize .NET tooling across development and CI by managing a per-repository tool manifest.

Core Features & Use Cases

  • Local tools defined in .config/dotnet-tools.json are versioned and restored with dotnet tool restore.
  • Per-repository scope avoids global tool conflicts and simplifies CI configuration.
  • Deterministic setups for teams and pipelines across local development and CI.

Quick Start

Initialize the manifest and restore tools locally with dotnet new tool-manifest and dotnet tool restore.

Frequently Asked Questions about dotnet-local-tools

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

FAQPage Schema
How do I keep .NET tool versions consistent across local dev and CI?▼

To keep .NET tool versions consistent across local dev and CI, use a per-repository tool manifest at .config/dotnet-tools.json. This file defines versioned local tools that are restored deterministically using the dotnet tool restore command.

What is a .NET local tool manifest used for?▼

A .NET local tool manifest is used to scope project-specific tools to a repository, avoiding global tool conflicts. Defined in .config/dotnet-tools.json, it ensures teams and automated pipelines use identical, deterministic tool versions during development and testing.

How do I set up dotnet local tools for my repository?▼

To set up dotnet local tools, initialize the manifest by running dotnet new tool-manifest. Add your required tools to the generated .config/dotnet-tools.json file, then execute dotnet tool restore to install the configured versions locally or in your build pipeline.

Can I use dotnet tool restore in CI pipelines to install project tooling?▼

Yes, you can use dotnet tool restore in CI pipelines to install project tooling. It reads the .config/dotnet-tools.json manifest and automatically installs the exact tool versions specified, ensuring deterministic builds and simplifying CI configuration without relying on global installs.

Why should I use per-repository .NET tools instead of global tools?▼

Per-repository .NET tools prevent version conflicts that arise from global installations. By using a local manifest, you ensure deterministic setups where developers and CI environments use identical tool versions, avoiding environment-specific build failures.

Do I need a manifest file to restore dotnet tools in a build pipeline?▼

Yes, you need a manifest file at .config/dotnet-tools.json to restore dotnet tools in a build pipeline. The dotnet tool restore command relies on this file to identify and install the exact tool versions required for deterministic builds.

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
sandraschisandraschi
18

matrix-theory-specialist

Explain advanced matrix theory with rigorous proofs and LaTeX examples.

Community
Advanced
psakepsake
1

psake

Automate task-based build scripts with the psake DSL for PowerShell projects.

Official
Advanced
rudironsonirudironsoni

dotnet-tool-management

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

Community
Intermediate