fabrikam-package-audit
Audit a .NET project's Fabrikam package references for v4 readiness — find v3-era Fabrikam.* packages, flag the ones that are renamed, version-bumped, or removed in v4, and report a per-package upgrade plan. Use when reviewing .csproj, Directory.Packages.props, or packages.config.
- License 许可
- MIT
- 最近更新
- 2026-10-24
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- fabrikam-package-audit
- metadata
- { "traits": ".NET|CSharp|VisualBasic|DotNetCore", "discovery": "lazy", "importance": "medium" }
- description
- Audit a .NET project's Fabrikam package references for v4 readiness — find v3-era Fabrikam.* packages, flag the ones that are renamed, version-bumped, or removed in v4, and report a per-package upgrade plan. Use when reviewing .csproj, Directory.Packages.props, or packages.config.
- requires-extension
- upgrade-fabrikam
03 SKILL.md 正文
Fabrikam package audit
On-demand guidance for reviewing a solution's Fabrikam package set before or during a v4 migration.
Steps
- Locate the package declarations:
.csproj<PackageReference>items, a centralDirectory.Packages.props, or legacypackages.config. - Call
detect_fabrikam_packagesto list everyFabrikam.*reference and its current version, thenplan_package_migrationfor the v4 target of each. - For each flagged package:
- Renamed (e.g.
Fabrikam.Logging→Fabrikam.Diagnostics) — remove the old reference, add the new one, and update namespaces. - Version-bumped (e.g.
Fabrikam.Data3.x → 4.0) — bump the version and review the breaking-change notes (async-only API in v4). - Removed (e.g.
Fabrikam.Json) — delete the reference and migrate callers to the recommended successor (System.Text.Json).
- Renamed (e.g.
- Summarize required changes and propose an ordered plan (shared/leaf projects first, then the apps that depend on them).
This skill is lazy: it loads only when the agent matches a package-review
task, keeping it out of the context window otherwise.
04 同仓库更多 Skills
fabrikam-v4-upgrade
Migrate a .NET solution from the Fabrikam v3 component suite to v4 — apply the package renames (Fabrikam.Web.Mvc → Fabrikam.AspNetCore.Mvc, Fabrikam.Logging → Fabrikam.Diagnostics, Fabrikam.Security.Tokens → Fabrikam.Identity.Tokens), bump Fabrikam.Data to 4.0, and drop Fabrikam.Json in favor of System.Text.Json.
fabrikam-package-audit
Audit a .NET project's Fabrikam package references for v4 readiness — find v3-era Fabrikam.* packages, flag the ones that are renamed, version-bumped, or removed in v4, and report a per-package upgrade plan. Use when reviewing .csproj, Directory.Packages.props, or packages.config.
fabrikam-controls-rules
Fabrikam UI control rules that apply during a .NET version upgrade — which Fabrikam.Windows.Forms versions are supported on modern .NET, what must be replaced rather than retargeted, and how the decision is recorded.
fabrikam-v4-upgrade
Migrate a .NET solution from the Fabrikam v3 component suite to v4 — apply the package renames (Fabrikam.Web.Mvc → Fabrikam.AspNetCore.Mvc, Fabrikam.Logging → Fabrikam.Diagnostics, Fabrikam.Security.Tokens → Fabrikam.Identity.Tokens), bump Fabrikam.Data to 4.0, and drop Fabrikam.Json in favor of System.Text.Json.
fabrikam-controls-rules
Fabrikam UI control rules that apply during a .NET version upgrade — which Fabrikam.Windows.Forms versions are supported on modern .NET, what must be replaced rather than retargeted, and how the decision is recorded.