Debug code using tools and evidence

Conduct investigation-heavy debugging with search and log evidence first

Investigation-heavy debugging when tool-driven evidence (search/logs/diffs) beats guesswork.

• · Error output/log, codebase, config assumptions

• · Root cause traced; one change per iteration; re-verified symptom

• · rg (regex search)
• · git diff/status
• · test/run commands

Single source of truth symptom available

• · Multiple changes at once; config assumptions incorrect
• · Symptom not re-verified

• · Prefer tool-driven evidence before code change
• · Control flow traced entrypoint → callers
• · One change at a time discipline