review-merge-readiness

Assess production readiness by executing a structured code review against git diffs, project plans, and requirements. This process categorizes issues by severity and provides a definitive merge verdict to prevent post-merge deployment risks.

Yes, you can request a code review that categorizes identified issues into Critical, Important, and Minor severity levels. This severity-based reporting provides clear prioritization for resolving bugs and architectural soundness before merging.

The best way to ensure alignment is to evaluate code changes against the original project plan and feature requirements. A structured review checks for functional bugs, architectural soundness, and adherence to ensure production readiness.

You request a code review by triggering the skill with phrases like "request code review" or "merge readiness." It then analyzes your current git diff to identify issues and deliver a clear verdict on mergeability.

Yes, the merge readiness review provides a definitive merge verdict after evaluating your code. It assesses production readiness based on identified issues and their severity levels, giving you a clear decision on mergeability.

You need a structured code review for git diffs before merging a new feature to the main branch. This ensures the code is functional, aligned with project requirements, and ready for production deployment without post-merge issues.