critic

Adversarial code review evaluates current git diffs against loaded contracts, specs, and design-system rules to identify and reject changes that drift from architectural intent. It enforces phase-based evaluation across spec compliance, architectural integrity, and security checks.

Architectural drift detection works by assessing uncommitted changes against loaded design-system rules and architectural intent. It identifies regressions where new code violates established contracts or architectural boundaries, providing deterministic outputs and actionable remediation guidance.

To check uncommitted git changes for spec compliance, load the current diff and run a phase-guided review against project contracts. The evaluation follows a structured load and context workflow to ensure alignment across affected files before commit.

Yes, adversarial review enforces security checks alongside contract validation. It applies phase-based evaluation that includes spec compliance, architectural integrity, content quality, and security checks to ensure deterministic outputs and actionable remediation guidance.

Yes, you can use contract validation for local changes before commit. The review process loads current uncommitted git changes and evaluates them against project contracts, specs, and design-system rules to ensure spec and architectural alignment before committing.

The best way to ensure architectural integrity is to run an adversarial review that assesses the diff against loaded contracts and design principles. This phase-guided workflow identifies contract violations and architectural drift across all affected files with actionable remediation.