review:pre-merge

Automating pre-merge code review involves analyzing git diff changes for correctness, security, and maintainability before merging. This skill orchestrates that assessment by applying structured checklists to each changed file and generating a report with remediation steps.

A thorough pre-merge checklist covers code correctness, test coverage verification, security vulnerabilities, refactor safety, and maintainability. It requires cross-referencing imports and analyzing working tree changes to produce actionable severity-rated issues.

Verifying test coverage and security before merging involves executing a senior-review specialist process on the git diff. It analyzes changed files against five checklists, cross-references imports, and outputs a structured pre-merge report with identified issues.

Yes, an automated senior review specialist can be used for pull request refactor safety analysis. It evaluates working tree changes, applies maintainability and security checklists, and produces a final pre-merge report detailing refactor risks and remediation steps.

The best way to analyze working tree changes is loading them via git diff and applying a multi-point checklist for correctness, tests, and refactor safety. This identifies severity-rated issues and generates suggested fixes in a structured pre-merge report.

Yes, a pre-merge code review report includes specific remediation steps for identified issues. The generated report provides severity ratings and actionable suggestions to resolve security, maintainability, and correctness problems before the final merge.