sumo-qa-reviewing-before-merge

To verify merge safety, you need an evidence-first review that analyzes your diff, discovers file:line risks, and runs fresh verification tests to confirm those risks are covered. This prevents merging changes that could break existing functionality.

Risk-to-test coverage mapping links each named risk found in your diff to a specific, freshly executed test that validates that failure mode. It acts as a verification gate, blocking the merge if any identified risk lacks a matching test.

An adversarial code review sweeps the diff to surface 3-7 named risks tied to exact file:line locations, then runs your test suite now to confirm those risks fail safely. This ensures your merge decision is backed by concrete evidence.

Fresh test evidence is required because relying on previous CI runs does not prove your current diff is safe. An Iron Law forbids declaring merge safety without running tests now and explicitly mapping each named risk to a matching test.

Yes, mutation testing and test planning help assess pull request risk by verifying that your tests catch introduced faults. This Skill uses similar verification gates to map discovered risks to fresh tests, ensuring your changes are safe to merge.

To find what could break, an adversarial sweep of your diff identifies 3-7 named risks at specific file:line locations. Fresh tests are then run to verify these failure modes, blocking the merge if any risk lacks test coverage.