troubleshoot

Systematic debugging of failing tests uses a structured five-step loop: Research, Hypothesize, Implement, Test, and Document. This workflow guides you through investigating failures, forming hypotheses, applying fixes, and verifying results in your codebase.

Documenting debugging progress in a worklog involves recording findings during the Research phase and updating the log after testing. This collaborative logging tracks reproducibility and ensures all codebase changes are documented for future reference.

Structuring a debugging workflow for a project context requires initiating a session within a designated space or issue number. The process applies the five-step debug loop to research the codebase, hypothesize fixes, implement snippets, and test outcomes.

This debugging approach supports both general project issue sessions and targeted test failure debugging. By referencing a specific project or issue context, the workflow adapts to investigate broad codebase problems or isolated test failures.

A structured debugging loop provides a disciplined approach to troubleshooting by ensuring you research, hypothesize, and document every step. Unlike ad hoc methods, it produces a worklog that guarantees reproducibility and tracks all codebase modifications.

Yes, this troubleshooting method requires spawning contextual research to investigate codebase errors effectively. This research phase initiates the five-step loop, allowing you to gather necessary findings before hypothesizing and implementing code snippets.