best-practice-check

To check for architectural drift and anti-patterns, run a pattern conformance analysis on your current module. This assesses whether your implementation aligns with established patterns and outputs a structured report detailing drift notes and maintainability risks.

Pattern conformance analysis evaluates how well your codebase aligns with established architectural patterns. You need it during design reviews or audits to detect drift, identify anti-patterns, and evaluate maintainability and scalability concerns without altering the code.

Assess code maintainability and scalability by running a conformance check on the subsystem. The process evaluates pattern alignment, identifies drift, and produces structured ratings for maintainability and scalability based on real-world approaches.

Pattern conformance analysis does not modify your source code. It performs a read-only evaluation of your implementation against known architectural patterns to detect drift and anti-patterns, generating a structured assessment report instead of altering files.

Yes, you can run a conformance check for architecture reviews without external dependencies. The Skill requires no setup tools or libraries, directly analyzing the given code scope to produce a conformance verdict, drift notes, and maintainability ratings.

The best way to detect pattern drift during an audit is to perform a structured conformance assessment. By researching real-world approaches and comparing them against your code scope, you identify architectural drift, anti-patterns, and maintainability concerns repeatably.