investigate-issue

To investigate a GitHub issue, you can fetch the issue details using GitHub CLI, analyze the codebase to identify affected areas, research external library documentation, and generate an actionable implementation plan with test guidance.

The best way to diagnose a bug is to classify the problem, search the codebase for relevant faulty code, research potential solutions using documentation, and present a clear plan for fixing it with necessary test recommendations.

Yes, you need GitHub CLI to fetch issue details. You also need Context7 and web search capabilities to research external library documentation for thorough analysis and accurate implementation planning.

You can use this issue investigation process for bug triage, feature planning, and documentation updates. It classifies the problem and identifies affected code areas to support various issue types.

After analyzing a GitHub issue and pinpointing the faulty code, this approach generates a detailed implementation plan that includes impact analysis and specific test recommendations to guide your code changes.

Researching external library documentation is required during issue investigation to understand the dependencies involved, verify expected behaviors, and formulate an accurate, actionable implementation plan.