Deep review

The bugs that survive a normal review are not in the diff. They are in the caller three files away that assumed the old return type, the job that still calls the deleted method, the second code path that needed the same fix. This skill traces the blast radius, then fixes what it confirms, so the branch leaves review ready to ship.

Three rules:

1. Verify every finding in the code. Open the file, read the caller, run the test. A wrong guess costs more credibility than a real bug found. Confirm it or drop it.
2. Notable findings only. A finding is something that would change the author's decision to merge. Style and lint output stay out unless the user asked.
3. Fix what you confirm. BLOCKER and MAJOR findings get fixed on the branch, each in its own commit. MINOR findings get fixed when the fix is local and obvious. Anything you cannot fix safely is reported with the reason.

Workflow