pipeline-code-reviewer

A pipeline code review enforces hexagonal architecture by tracing real imports across modified files to verify dependency direction, ensuring Adapters point to Application and Domain layers without reverse coupling. It flags domain or framework coupling as critical issues to prevent boundary violations.

Evidence-based code review inspects the actual repository source to detect dead code, code duplication, and reusability issues beyond the diff. It verifies design compliance and flags CRITICAL or MAJOR issues without approving unverified claims.

Yes, a pipeline quality gate performs strict security spot-checks to look for hardcoded secrets, authorization gaps, unsafe input usage, sensitive data leakage, and insecure patterns. It validates these security postures using evidence from the actual codebase.

Revision-loop validation re-reads original files to prove whether previous issue fixes truly exist without regressions. It verifies that prior CRITICAL and MAJOR flags are resolved by checking the actual codebase evidence rather than trusting claims.

The best way to verify dependency direction is using a deep code review tool that traces real imports across new or modified files. It checks that dependencies flow correctly from Adapters to Application to Domain, flagging any domain or framework coupling violations.