convert-to-cpm

Converts .NET projects and solutions to Central Package Management format via a Directory.Packages.props file.

Updated May 28, 2026
One-click install
npx skills add https://github.com/ojrojas/AgentsInstructions --skill convert-to-cpm-ojrojas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convert-to-cpm
Source: https://github.com/ojrojas/AgentsInstructions/tree/main/.claude/skills/dotnet-nuget/skills/convert-to-cpm
Command: npx skills add https://github.com/ojrojas/AgentsInstructions --skill convert-to-cpm-ojrojas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing scattered package versions across multiple .NET projects, enabling users to convert to Central Package Management (CPM) for a unified and efficient version control.

Core Features & Use Cases

  • Convert to CPM: Migrate .NET projects and solutions to CPM, centralizing package versions in a single Directory.Packages.props file.
  • Version Conflict Resolution: Detects and resolves version conflicts between packages across projects, ensuring consistency.
  • Baseline Build Capture: Captures a baseline build state before making changes for comparison after conversion.
  • Post-conversion Report: Provides a detailed report summarizing the conversion process, version changes, and follow-up items.

Quick Start

Convert your .NET project to CPM by running the command: convert-to-cpm --scope <project/solution/repository>

Frequently Asked Questions about convert-to-cpm

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

FAQPage Schema
How do I convert .NET projects to Central Package Management?

To convert .NET projects to Central Package Management, the Skill migrates solutions by centralizing NuGet package versions into a single Directory.Packages.props file. It requires the .NET SDK and projects using the PackageReference format.

What is Central Package Management for NuGet and when do I need it?

Central Package Management (CPM) is a mechanism that centralizes scattered NuGet package versions across multiple .NET projects into one Directory.Packages.props file. You need it to enforce version consistency and simplify package updates across large solutions.

How does Central Package Management handle NuGet version conflicts during conversion?

During CPM conversion, the Skill detects version conflicts between packages across different projects and resolves them to ensure consistency. It centralizes the resolved versions in the Directory.Packages.props file and reports the changes.

Does Central Package Management conversion work with packages.config or only PackageReference?

CPM conversion only works with .NET projects using the PackageReference format. Your project files must already be using PackageReference before you can migrate them to the centralized Directory.Packages.props format.

What is the best way to track NuGet version changes after migrating to Central Package Management?

The best way to track changes is by capturing a baseline build state before conversion. The Skill compares against this baseline and generates a comprehensive post-conversion report summarizing version changes and follow-up items.