convert-to-cpm
Skill0 starsChanged 49 days agoLicence not identifiedView on GitHub
Convert .NET projects and solutions (.sln, .slnx) to NuGet Central Package Management (CPM) using Directory.Packages.props. USE FOR: converting to CPM, centralizing or aligning NuGet package versions across multiple projects, inlining MSBuild version properties from Directory.Build.props into Directory.Packages.props, resolving version conflicts or mismatches across a solution or repository, updating or bumping or syncing package versions across projects. Also activate when packages are out of sync, drifting, or inconsistent -- even without the user mentioning CPM. Provides baseline build capture, version conflict resolution, build validation with binlog comparison, and a structured post-conversion report. DO NOT USE FOR: packages.config projects (must migrate to PackageReference first) or repositories that already have CPM fully enabled.
In this repository41 other files it gives its agents.
- agentic-actions-auditorSkill
- alerting-irmSkill
- analyzing-dotnet-performanceSkill
- angular-developerSkill
- brainstormingSkill
- cloudflare-oneSkill
- configuring-opentelemetry-dotnetSkill
- create-datadriven-aspnetcoreSkill
- csharp-refactoringSkill
- dashboardingSkill
- design-taste-frontendSkill
- dev-referencesSkill
- dotnet-trace-collectSkill
- dotnet-webapiSkill
- dump-collectSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- gh-stackSkill
- grillingSkill
- grill-meSkill
- kotlin-tooling-java-to-kotlinSkill
- lokiSkill
- microbenchmarkingSkill
- migrate-dotnet10-to-dotnet11Skill
- migrate-dotnet9-to-dotnet10Skill
- migrate-nullable-referencesSkill
- optimizing-ef-core-queriesSkill
- playwright-cliSkill
- prometheusSkill
- promqlSkill
- requesting-code-reviewSkill
- ruffSkill
- subagent-driven-developmentSkill
- supply-chain-risk-auditorSkill
- systematic-debuggingSkill
- test-anti-patternsSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- uvSkill
- verification-before-completionSkill
- writing-plansSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 10 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.