converting-to-cpm Skill
Converts .NET projects and solutions to NuGet Central Package Management (CPM) with Directory.Packages.props. Use when the user wants to centralize, convert, align, or sync NuGet package versions across multiple projects, resolve version conflicts or mismatches, or get versions consistent across a solution or repositor Published by microsoft in upgrade-agent-plugins.
What is converting-to-cpm Skill?
Converts .NET projects and solutions to NuGet Central Package Management (CPM) with Directory.Packages.props. Use when the user wants to centralize, convert, align, or sync NuGet package versions across multiple projects, resolve version conflicts or mismatches, or get versions consistent across a solution or repositor Published by microsoft in upgrade-agent-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using upgrade-agent-plugins
Technical details
- Install or run with Copy skill directory
When to use converting-to-cpm Skill
- Use it for developers using upgrade-agent-plugins.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/upgrade-agent-plugins
- Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/common/converting-to-cpm/SKILL.md
What it does
Converts .NET projects and solutions to NuGet Central Package Management (CPM) with Directory.Packages.props. Use when the user wants to centralize, convert, align, or sync NuGet package versions across multiple projects, resolve version conflicts or mismatches, or get versions consistent across a solution or repositor
Skill instructions
Convert to Central Package Management Migrate .NET projects from per-project package versioning to NuGet Central Package Management (CPM), centralizing all package versions into a single Directory.Packages.props. When to Use - User wants to adopt CPM for a repository, solution, or project - Package versions are scattered across project files and the user wants a single source of truth - User mentions Directory.Packages.props, CPM, or centralizing NuGet versions - User wants to align or sync a package version across multiple projects — suggest CPM if not already enabled - Package versions are out of sync or conflicting across projects When Not to Use - CPM is already fully enabled for all in-scope projects - Projects use packages.config (must first migrate to PackageReference) - User explicitly wants a custom MSBuild property file without CPM Inputs | Input | Required | Description | |-------|----------|-------------| | Scope | Yes | A project file, solution file, or directory containin
Explore related resources
Frequently asked questions
What is converting-to-cpm?
converting-to-cpm is a open-source AI agent skill with Copy skill directory. Converts .NET projects and solutions to NuGet Central Package Management (CPM) with Directory.Packages.props.
Who is converting-to-cpm best for?
converting-to-cpm is best for reusing agent instructions, scripts, and references.
How do I install converting-to-cpm?
Install or run converting-to-cpm using Copy skill directory. Check converting-to-cpm for the latest setup command.
Is converting-to-cpm actively maintained?
converting-to-cpm may need a closer maintenance check before production use.
Auto-fetched from GitHub.
