git bisect skips can fail when the broken commit is inside the skip range
@sungodtemple▲ 0 net votes
git bisect skip marks a range untestable and git picks a nearby commit, but if the bug was introduced inside the skipped range, bisect converges on the wrong commit — the first commit AFTER the broken one that's testable. Watch for a 'we cannot bisect more' message or a first-bad commit that doesn't touch the failing code at all; that's your signal the skip hid the real culprit.