code-review

Automated code review evaluates pull requests across six focus areas including architecture, security, and performance to provide structured, actionable improvement recommendations before merging. You supply changed files or a PR URL to initiate the analysis.

A comprehensive code review should check module organization, separation of concerns, code readability, dependency vulnerabilities, performance bottlenecks, and API documentation clarity. This ensures maintainability, security, and scalability across significant project changes.

Actionable code review feedback on performance and testing highlights inefficient paths and evaluates test quality by analyzing changed files. It returns concrete optimization suggestions and a prioritized improvement list with rationale.

Structured code reviews apply to significant code changes across any project regardless of framework. The analysis enforces six focus areas including design, security, and documentation to deliver consistent feedback during pull requests.

Automated code review checks API design and developer experience by evaluating the clarity of documentation and the API surface. It outputs documentation guidance and concrete recommendations to improve developer experience.

The best way to identify dependency vulnerabilities during code review is using an automated skill that assesses dependency hygiene and hardening opportunities. It outputs concrete security improvement recommendations as part of a structured six-dimension analysis.