convention-learner

The skill detects .NET coding conventions by analyzing existing repository patterns via project graph and public API snapshots, honoring explicit .editorconfig and Directory.Build.props rules before enforcing naming, structure, and style consistency.

Convention detection learns structure patterns using get_project_graph and validates type and naming conventions via get_public_api, ensuring consistency across architecture layers while respecting .editorconfig and Directory.Build.props configurations.

Yes, explicit .editorconfig and Directory.Build.props rules are honored before imposing generic defaults, ensuring configuration-aware enforcement that respects your established project-specific style and naming standards over detected patterns.

The best way to review code for convention violations is to generate a convention summary from existing patterns, then flag deviations in naming, folder structure, tests, and style while tracking recurring anti-patterns for documentation.

You should run repository analysis when joining an existing solution, generating new code, or reviewing code for convention violations, ensuring new contributions match the team's existing naming, folder structure, tests, and style configuration.

Yes, convention enforcement works without explicit .editorconfig by learning real conventions from the existing codebase, though it prioritizes honoring explicit .editorconfig and Directory.Build.props rules to ensure configuration-aware enforcement when available.