EDC

Enables ultra-granular, line-by-line code analysis to build deep architectural context for any codebase.

Reviews whether code changes deliver the stated goal/spec and fit the repository architecture. Use this for PRs, branches, task implementations, plans, or diffs when the question is whether the implementation built the right thing in the right place: requirement coverage, scope creep, module ownership, source-of-truth choices, contracts, migrations, docs, and rollout.

Performs security/adversarial differential review of code changes (PRs, commits, diffs). Use this for auth, validation, trust-boundary, injection, crypto, memory-safety, external-call, state-mutation, or security-regression risk. It leverages git history and edc-context for blast radius and writes markdown security reports.

Builds or updates deep architectural context for any codebase (v2 layout)

Incrementally updates edc-context/ files based on branch changes (v2 layout)

Identifies code quality, maintainability, overengineering, bloat, duplication, and test-value risks by comparing EDC context expectations to actual code

Constrained doc-only edit pass for generated EDC context after report-only curation.

Report-only whole-context curation pass for generated EDC context quality.