investigate

To find the root cause of a runtime error or failed deployment, use a four-phase debugging method: investigate, analyze, hypothesize, and implement. This systematically traces issues across code, configs, and data to ensure fixes address the actual cause.

Troubleshooting performance regressions in multi-service setups requires systematically gathering context across services using tools like Bash, Grep, and Glob. A structured investigation method helps trace malfunctions through code and configurations to pinpoint the underlying issue.

A structured root-cause debugging method works through four phases: investigating to gather evidence, analyzing the context, forming a hypothesis about the bug, and implementing a proposed fix. This prevents patching symptoms and ensures the actual cause is resolved.

Yes, you can debug flaky integrations using this method. The investigation process applies to runtime errors, failed deployments, and integration issues by leveraging Bash, Read, Grep, and WebSearch to gather evidence across your codebase and propose corrective actions.

Quick fixes fail when they address symptoms rather than the root cause. By applying a four-phase investigation—gathering evidence, analyzing, hypothesizing, and implementing—you ensure the actual source of the bug is identified and corrected.

No special environment setup is required to troubleshoot code and data configurations. The method leverages standard command-line tools like Bash, Read, Write, Edit, Grep, and Glob to gather context and propose remedies directly within your existing workspace.