cmd-workflow-team-review

A comprehensive code review of a feature branch coordinates feedback across security, quality, testing, and language-specific concerns. It uses a phase-driven process covering context, high-level analysis, line-by-line scrutiny, and final summaries to reduce defects.

Conduct a structured feature branch code review by following a phase-driven workflow: analyze the diff for context, evaluate high-level concerns, perform line-by-line scrutiny, and summarize with severity labels and a clear decision gate to approve or request changes.

Yes, you can enforce severity labels and decision gates during code reviews. The workflow guides reviewers through structured feedback, applying severity labels and concluding with a defined decision gate to Approve, Comment, or Request Changes.

Yes, the code review workflow supports language-specific analysis. It coordinates a comprehensive review of a feature branch, explicitly emphasizing security, quality, testing, and language-specific considerations alongside general maintainability and performance.

You need a phase-driven code review process when evaluating feature branches in development workflows before merging. It ensures reviewers fully understand changes through pre-submission diff analysis and provide multi-perspective feedback across security and quality.

The best way to review code changes for security and maintainability is using a multi-perspective workflow that separates feedback into Context, High-Level, Line-by-Line, and Summary phases, ensuring thorough scrutiny of correctness, performance, and security.