review-code

Automated code review for changed files uses a plan ID or plan path to load context, identify modified files via git diff or task summaries, and apply seven review lenses to generate structured findings.

The seven code review lenses are Plan Compliance, Correctness, Security, Conventions, Edge Cases, Test Quality, and Code Quality. Each lens evaluates changed files to produce structured findings with seven fields per issue.

Plan-based code review identifies files to evaluate by reading task summaries or executing git diff strategies to determine changed files, then reads the diffs for context before applying the seven review lenses.

Yes, you can generate a review file for downstream automation. The review process writes structured findings to a designated code-reviews path within the workspace and returns a concise summary suitable for automated workflows.

Yes, a seven-lens code review relies on the workspace layout under ~/.claude/projects. It uses the read-plan mechanism and the code-review-lenses reference to coordinate context loading, diff reading, and findings generation.

To ensure code quality across plan compliance and edge cases, apply a multi-lens code review approach. Evaluating changed files against predefined lenses like Correctness, Security, and Test Quality systematically captures issues and outputs structured findings.