bug-hunter

Gather more context first: the environment (dev, staging, prod), browser or device, user actions preceding the failure, and any error logs. Intermittent bugs often require checking for race conditions, timing issues, or environment-specific configuration differences.

Trace backward from the symptom through each layer of the code until you find where the actual problem originates. Use logging, breakpoints, and binary search checkpoints to narrow the problem space, then fix the root cause rather than masking the symptom.

Run git bisect start, mark the current commit as bad with git bisect bad, and mark a known working commit as good with git bisect good <hash>. Git checks out intermediate commits for you to test until it isolates the commit that introduced the bug.

This happens when you call an async function without await, so you receive a pending Promise instead of the resolved value. Add await before the call, or use .then(), and ensure the enclosing function is declared async.

Avoid heavyweight processes for trivial typos or syntax errors that linters and compilers catch instantly. The full reproduce-hypothesize-test workflow is most valuable for non-obvious, intermittent, or production bugs where guessing wastes time.