context-auditor

To audit code for architectural risks, you analyze the codebase structure, interfaces, and existing patterns to identify affected modules and potential circular dependencies. This process generates an Impact Report detailing new dependencies and an overall risk score.

Codebase architecture analysis for feature requests is the process of scanning file structures, PLAN.md, and interface files to determine module and protocol impact. It identifies potential SOLID principle violations to prevent costly implementation mistakes.

To check for SOLID principle violations, you scan your interfaces and file structure to detect SRP and LSP violations. This analysis identifies potential architectural risks and new dependencies within the codebase prior to implementation.

Yes, you can detect potential circular dependencies by scanning file structure and interface files. The analysis evaluates module and protocol impacts for proposed changes, highlighting these risks within an overall Impact Report.

The best way to identify module and protocol impact is to analyze existing codebase patterns and interface definitions. This generates an Impact Report that scores overall risk and details affected components for your proposed changes.

Yes, architecture risk assessment works without external dependencies by analyzing internal codebase structures, PLAN.md, and interface files. It independently evaluates existing patterns to generate a comprehensive risk score and Impact Report.