ia-code-review

Automated code review for a feature branch diff produces structured, severity-ranked findings by verifying spec compliance before assessing code quality. It audits the git diff for correctness, maintainability, security, performance, and test coverage using reference checklists.

Verifying PR spec compliance before merging requires a two-stage review process that first checks the implementation against the intended PR spec, then evaluates code quality. This ensures missing requirements and real defects are caught early.

Large pull request diffs can be reviewed using a multi-agent specialist deep review mode. The system analyzes diff signals to automatically dispatch dedicated specialist lenses for a more thorough audit of complex changes.

Merge-base comparison for branch code reviews auto-resolves the review scope from git state and calculates the correct delta between branches. This avoids reviewing the wrong diff and ensures accurate branch-review scenarios.

Yes, ia-code-review operates without external dependencies. It uses bundled reference checklists to enforce review mode selection via diff signals and dispatches automated specialists for security audits and spec compliance checks.

Auditing diffs for security and performance is limited to the scope of the provided git diff and merge-base comparison. It relies on diff signals to select review modes, meaning unreviewed deltas or incorrect base branches may affect audit accuracy.