semantic code review

Semantic Code Review for TypeScript PRs

Semantic code review catches code changes that are technically valid but semantically wrong for the system.

Semantic code review evaluates whether code preserves the meaning a team already approved in documentation, architecture decisions, and product rules. AxiomGuard implements this with approved SemanticRule YAML, deterministic TypeScript analysis, and proof-carrying findings.

Why it matters

Proof beats plausible review comments.

Approved SemanticRules are the source of truth.

Deterministic symbolic evidence creates PROVEN findings.

Only approved critical rules in block mode can stop a merge.

Use cases

Where teams apply this first.

FAQ

Questions about semantic code review.

How is semantic code review different from linting?

Linting checks generic style and syntax rules. Semantic code review checks project-specific intent, such as domain boundaries, side-effect rules, and business invariants.

Can semantic code review block a pull request?

AxiomGuard can block only when an approved critical SemanticRule produces a PROVEN deterministic finding in block mode.