Does this skill support Central Package Management (CPM)?

Yes, it is specifically designed to enforce CPM by flagging hardcoded version attributes in .csproj files and ensuring versions are defined in centralized props files.

What is the primary purpose of the .NET Architecture Linter?

The skill ensures .NET projects follow strict architectural patterns for package versioning and MSBuild file structures, specifically focusing on Central Package Management.

Which files are allowed to import Version.props?

By default, the linter only allows imports from Directory.Packages.props, eng/Directory.Build.props, and specific SDK entry points to prevent circular or hidden dependencies.

How does it handle version variable naming?

It follows a strict convention that removes dots and dashes from package names and appends 'Version', ensuring a consistent naming schema across the entire repository.

.NET Architecture Linter

Name: .NET Architecture Linter
Author: ANcpLua

byANcpLua

•

Developer Tools

Enforces MSBuild architectural standards and Central Package Management best practices across .NET solutions.

About

The .NET Architecture Linter is a specialized Claude Code skill designed to maintain clean and consistent MSBuild structures within complex .NET repositories. It automatically scans projects for violations related to Central Package Management (CPM), ensuring that package versioning is handled through centralized property files rather than hardcoded in individual project files. By enforcing strict rules like symlink verification for Version.props and preventing unauthorized imports in unexpected files, it helps platform engineers and developers avoid dependency drift and maintain a scalable, production-grade build infrastructure.

Key Features

Automates standard variable naming for package versions based on project conventions.
Validates Version.props import ownership across Directory.Packages.props and SDK entry points.
Detects and flags illegal local <PackageReference Version='...'> attributes in .csproj files.
Verifies symlink integrity for shared versioning files to prevent accidental file duplication.
1 GitHub stars
Identifies hardcoded package versions to enforce Central Package Management (CPM) compliance.

Use Cases

Auditing legacy .NET repositories to migrate from local versions to Central Package Management.
Automating code reviews for MSBuild and project file changes to ensure architectural alignment.
Standardizing package versioning across large-scale .NET microservices and monorepos.

About

Key Features

Automates standard variable naming for package versions based on project conventions.
Validates Version.props import ownership across Directory.Packages.props and SDK entry points.
Detects and flags illegal local <PackageReference Version='...'> attributes in .csproj files.
Verifies symlink integrity for shared versioning files to prevent accidental file duplication.
1 GitHub stars
Identifies hardcoded package versions to enforce Central Package Management (CPM) compliance.

Use Cases

Auditing legacy .NET repositories to migrate from local versions to Central Package Management.
Automating code reviews for MSBuild and project file changes to ensure architectural alignment.
Standardizing package versioning across large-scale .NET microservices and monorepos.