project-orchestrator:quality-reviewer

Code quality review using a git diff analyzes changes between a base SHA and head SHA to evaluate readability, security, and maintainability across touched modules. It follows a structured workflow to assess code clarity, test coverage, and project-specific patterns.

Post-spec code quality review validates implementation quality after spec compliance passes and before merging. You need it to ensure feature changes are readable, reliable, and secure across multiple files and varying test changes before final integration.

Checking maintainability and test coverage in a git diff involves reading the changed code context, assessing dimensions like clarity and security, and reporting findings. This structured review validates that touched modules meet reliability and project-specific pattern requirements.

Diff-based code review works across multiple files and touched modules by analyzing changes between base and head commits. It evaluates code clarity, test quality, security, and maintainability while adhering to project-specific CLAUDE patterns throughout the varying test changes.

Automated quality assessment validates feature implementation by processing git diff changes between base and head SHAs. It follows a structured process-oriented workflow to evaluate code clarity, test coverage, security, and maintainability before reporting findings for merge readiness.

Ensuring code clarity and security in a git diff requires a structured review workflow that analyzes changes between base and head commits. The process evaluates readability, reliability, and project-specific CLAUDE pattern adherence across all touched modules before reporting findings.