requesting-code-review

To perform an automated code review before a git merge, analyze git diff ranges to catch defects early. This skill categorizes identified issues by severity and provides actionable feedback to ensure clean releases.

Reviewing git diff ranges for pull requests involves comparing commit ranges to identify changes and categorize defects. This approach provides a readiness assessment and clear recommendations for developers before merging.

Severity categorization in pre-merge code reviews classifies findings into Critical, Important, and Minor issues. This helps developers prioritize bug fixes and security issues systematically before merging code.

Yes, you can apply this automated code review to any git repository during development. It is ideal after completing a development task or before a pull request is merged to ensure consistent review standards.

You need to run a pre-merge code review when completing a development task or preparing a pull request. This catches bugs, security issues, and technical debt early, providing a merge readiness assessment.

Automated git diff analysis supplements manual pull request reviews by systematically catching defects and categorizing severity. It ensures consistent review standards and provides actionable feedback, but developers still make the final merge decision.