etherweave-code-review

Automated code review for pull requests evaluates staged or unstaged changes against project rules, architecture boundaries, and fitness functions. It enforces type hints, documentation, security practices, and performance considerations to generate structured critiques with actionable suggestions.

Architecture conformance checking verifies adherence to layer, port, and adapter rules within a codebase. It ensures changes respect established architecture boundaries and structural requirements, preventing violations that compromise system design during pull request reviews.

Yes, compliance checks can be applied to unstaged changes before a pull request. The review process verifies code against project rules, architecture boundaries, and quality standards, ensuring type hints and documentation meet formal compliance requirements.

Verifying security practices and performance considerations during code review requires checking changes against project rules and a master AI reference. This approach reduces risks by enforcing security standards and evaluating performance impacts before merging pull requests.

Code review automation relies on predefined project rules, a master AI reference, and architecture boundaries to function. Without these established compliance standards and fitness functions, the automated review cannot enforce type hints, documentation, or security practices effectively.