requesting-code-review

Automated code review is performed by dispatching a reviewer subagent to validate quality and compliance. It enforces a self-review checklist, gathers file diffs and recent commits, and categorizes feedback into critical, important, and minor issues before merging.

A systematic code review checklist guides developers to verify conventions, tests, and security before involving a reviewer. It ensures structured peer review by standardizing the output format and validating code compliance before merging changes.

Code review automation integrates with git workflows by automatically gathering changed files, diff summaries, and recent commits. It applies to software development teams after bug fixes, feature completions, or any code modification requiring peer review.

Code review findings are categorized into critical, important, and minor issues, with defined actions for each category. This severity classification helps prioritize software quality fixes and ensures critical defects are addressed before merging.

A structured peer review is needed after tasks, major feature completions, bug fixes, or any code modification requiring validation. It prevents defects and enforces software quality by validating compliance before changes are merged.

Yes, a self-review checklist guides developers to verify conventions, tests, and security independently. This pre-review step ensures code quality before dispatching a reviewer subagent for the final pull request evaluation.