review-merge

To automate a final code review before merging, the skill verifies task completion, validates code review status, and runs integration checks including rebasing and test suites to ensure the feature branch is production-ready.

Verifying preconditions for a git merge involves checking that all task phases are marked complete, confirming code reviews have passed, and running comprehensive tests to detect merge conflicts before deployment.

Yes, you can scan for forbidden files and sensitive data before deploying to production, as the skill performs forbidden file scans during its integration testing phase to prevent unauthorized changes.

You generate an executive summary of code changes for production deployment by using the skill to create a CEO-readable summary detailing the changes, their impact, and required post-merge steps.

Yes, the merge review process prepares the actual git merge commands for you, alongside generating an executive summary and outlining any necessary post-merge steps to finalize the deployment.

Your feature branch needs rebase and test suite validation before integration to ensure it integrates cleanly with the main branch, preventing merge conflicts and verifying code stability as a final quality assurance step.