branch-review-before-pr

To run a pre-merge code review, execute the command `/branch-review-before-pr` to analyze branch differences and detect race conditions, trust boundary violations, and query safety issues. It flags blocking issues and informational references to ensure code integrity.

Pre-merge code review is the process of analyzing differences between a current branch and the main branch to identify security vulnerabilities and functional issues. You need this check before merging to prevent integration conflicts and mitigate critical security risks.

Yes, you can customize the code review checklist for specific project requirements. The Skill uses a detailed checklist for analysis that allows customization to meet specific project requirements, ensuring targeted detection of data integrity and authentication issues.

Yes, you need Git installed to conduct a pre-merge security check. The Skill requires Git to analyze differences between the current branch and the main branch, and it uses specific analysis scripts to check for query safety, race conditions, and trust boundary violations.

The best way to identify trust boundary violations is by running a comprehensive pre-merge code review. The Skill analyzes your source code repositories using specific scripts to detect trust boundary violations, query safety issues, and race conditions before merging.

A pre-merge review flags informational issues instead of blocking the merge because these are non-critical references rather than severe security vulnerabilities or functional problems. The Skill distinguishes between critical blocking issues that halt merging and informational issues for developer reference.