review

To check code changes against architectural principles, you can run an architectural review using a principles document. This detects semantic violations, such as business logic in the wrong layer, that static analysis tools often miss.

Semantic code analysis evaluates code changes against defined architectural principles to identify design-intent issues. It detects complex protocols or misplaced business logic within layered architectures that standard static analysis cannot catch.

To review your last commit for architectural violations, run the review skill with the diff range set to HEAD~1. This checks the recent code changes against your specified principles document and reports violations with suggested fixes.

Architectural review is specifically suitable for projects with layered architectures. Without a layered structure and a defined principles document to provide context, the semantic analysis cannot accurately detect design-intent violations.

Architectural review catches design-intent violations that static analysis misses by checking code changes against a principles document. While static analysis checks syntax and formatting, semantic analysis identifies misplaced business logic or complex protocols.

Yes, you need a principles document to run a semantic code review. The document provides the necessary context for the semantic analysis to evaluate code changes and detect architectural violations within your layered architecture.