create-inspection

To investigate a flaky test failure, you need a structured root cause analysis that examines code, tests, and logs to identify the actual source with file citations, rather than just treating symptoms. This process generates evidence-backed decision documents outlining viable fix paths.

The best way to plan code debugging for a performance regression is to generate a multi-option fix comparison. This includes evaluating at least two distinct approaches with clear tradeoffs, effort estimates, and risk assessments to avoid wasted effort on suboptimal solutions.

Pre-fix evaluation for authorization token race conditions works by investigating the specific technical problem across the codebase to produce a structured decision document. It outlines viable fix paths with associated tradeoffs and saves the output to a project's docs directory for stakeholder review.

Yes, you can use root cause analysis for misconfiguration issues. It applies to pre-fix evaluation workflows across software engineering codebases, generating evidence-backed diagnoses with mandatory file:line citations for all claims to ensure accurate problem resolution.

You need a tradeoff assessment before implementing a non-trivial bug fix to eliminate guesswork and rushed, poorly evaluated fixes. This saves development time and reduces the risk of introducing new issues by fully understanding the problem before acting.