context-building

To build context before debugging, investigate the codebase using a structured workflow for problem understanding, codebase search, code analysis, and dependency tracing to produce a concise context summary before proposing a fix.

The best way to trace dependencies for bug triage is to map imports, data flow, and side effects across modules, which systematically gathers context to prevent misdiagnosis and scope creep during incident response.

You investigate a codebase by describing the problem, locating relevant files through codebase search, and synthesizing a structured context summary with actionable questions to fully understand the issue before addressing it.

Yes, you can use a structured investigation workflow for feature refinement and incident response. It enforces systematic context gathering across debugging and bug triage to ensure deep understanding of code and dependencies.

Gathering context before addressing issues prevents scope creep by enforcing an investigation workflow that maps dependencies and data flow, ensuring you fully understand the problem and produce actionable questions rather than guessing.