code-reviewer

Architecture conformance is checked by verifying codebase alignment with architecture decisions, ADRs, and OpenAPI contracts. The review identifies anti-patterns and maintainability risks without modifying source files, outputting structured findings to the .forgewright/code-reviewer/ directory.

Automated spec compliance and code quality reviews use a two-stage process: first verifying alignment with BRD/PRD criteria and architecture decisions, then assessing SOLID, DRY, error handling, logging, and maintainability to surface production-grade validation issues early.

A two-stage code review process works by first confirming spec compliance against architecture decisions and contracts, then evaluating code quality across SOLID, DRY, error handling, and logging for backend services, frontend apps, and libraries.

Read-only code review can run against a repository without modifying source files. It surfaces architectural and quality findings by applying production-grade validation to backend services, frontend apps, and libraries, writing structured artifacts to .forgewright/code-reviewer/.

Static analysis for code quality enforces BRD/PRD criteria by applying a spec compliance check followed by a code quality review. It validates alignment with these requirements and surfaces architecture conformance issues and anti-patterns early in the development cycle.

Reviewing code quality without modifying source is limited to identifying and reporting architecture conformance issues and maintainability risks. It generates structured artifacts and reports but does not fix or rewrite the detected anti-patterns in the codebase.