triage-issue

To find the root cause of a bug, you need agent-based codebase exploration that investigates entry points, code paths, and recent changes. This process focuses on observable contracts to locate the underlying failure mode rather than just treating symptoms.

You can create a GitHub issue with a TDD fix plan by using agent exploration to diagnose the defect and then generating a structured RED-GREEN test cycle. This plan specifies minimal implementation changes and behavior contracts directly within the issue.

The best way to plan a test-driven development fix is to produce an ordered RED-GREEN cycle list. This approach identifies the smallest change needed to address the failure and specifies observable behavior contracts that must be verified.

Yes, effective bug triage requires investigating recent code changes and error handling to determine the root cause. Exploring these relevant code paths ensures you understand the observable contracts and can plan a reliable fix.

You need to triage a GitHub issue when a user reports a vague defect and you require root-cause reasoning before acting. This ensures you move from a simple bug report to a concrete, safe TDD-based fix plan.

You can use it to investigate failing behavior and generate a test plan, but you still need to execute the plan. It produces the structured RED-GREEN test cycle list that specifies the minimal implementation changes required for the fix.