Will It Vibe?Debugger breakpoint left in source
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
binding.pry, byebug, and debugger stop the process and wait for a console attached to STDIN. If a code path carrying one of these ever runs in production, that request, or the whole worker on a single-threaded server, hangs waiting for a developer who is not there.
Why it matters
binding.pry, byebug, and debugger all pause the current thread and wait for an interactive console attached to STDIN. A production server has nothing attached to STDIN, so a request that reaches one of these lines does not error, it hangs, tying up a worker (or in some deployments the entire single-threaded process) until it is killed and restarted.
How to fix it
Delete the leftover breakpoint line. If a linter (Rubocop with rubocop-rspec or a custom cop) is available in this project, consider enabling a check that flags these calls automatically so the next one gets caught before it merges rather than after it ships.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo