requesting-code-review

Automated code review is facilitated by dispatching a specialized subagent to analyze your changes against implementation plans and quality standards. It categorizes feedback into critical, important, and minor issues to ensure production readiness.

Checking code quality before merging is handled by running a structured review process that identifies architectural flaws and bugs. It evaluates code quality, testing coverage, and requirements adherence to verify production readiness.

An automated code reviewer categorizes feedback by separating identified issues into critical, important, and minor levels. This structured feedback covers code quality, architecture, testing, and requirements to ensure development workflow adherence.

Yes, you can dispatch a code-reviewer subagent to analyze code changes directly against your implementation plan. It checks for production readiness and adherence to quality standards before merging.

Yes, the automated code review process operates without external dependencies. It uses internal scripts and references to analyze code changes and identify architectural or testing issues.

You should request an automated code review after completing a new feature to catch potential bugs or architectural flaws early. This ensures your code changes meet requirements and quality standards before merging.