investigate

To find the root cause of a software crash, you need a systematic process for error reproduction, detailed error message analysis, and code investigation to pinpoint the exact failure. This Skill guides you through these steps to identify the underlying issue.

Systematic bug fixing involves understanding error messages in detail, reproducing the failure accurately, and tracing the issue to the specific code or data causing the problem. This approach ensures you address the actual problem rather than just treating symptoms.

Investigating a software panic requires guiding through error reproduction and root cause identification to locate the exact code triggering the failure. This ensures the minimal fix proposed resolves the core issue rather than masking the panic.

Systematic analysis requires a clear error description and an understanding of the affected codebase to accurately identify and resolve the root cause. Without a precise error message, reproducing the failure and pinpointing the faulty code becomes significantly more difficult.

To ensure a bug fix does not introduce new issues, you need regression testing to verify the correction does not break existing functionality. This Skill includes proposing a minimal change and validating it through regression testing to prevent new failures.

The minimal fix approach for code investigation findings involves suggesting the smallest possible change needed to address the identified root cause. This prevents unnecessary code modifications while resolving the software failure or panic.