issue-resolution

Root cause analysis for a failing test requires iteratively forming hypotheses, gathering evidence through code path tracing, and documenting findings. This Skill guides that process to produce an auditable RCA document and verified fix plan.

The best way to triage unexpected behavior is normalizing diverse issue reports into a concise brief, then planning deterministic reproduction. This workflow ensures you create reliable test cases that consistently trigger the bug before analysis.

Yes, this workflow includes impact assessment and risk profiling to prioritize fixes. It decomposes fixes into manageable steps with traceability to the RCA, ensuring safe deployment across affected code and test environments.

You create an auditable history for bug resolution by following a structured workflow with defined checkpoints and artifacts. This Skill requires referencing those artifacts throughout triage, RCA, and verification to maintain traceable records.

You should use a structured bug triage workflow when resolving complex bugs, failing tests, or unexpected behavior that requires verified fixes and traceable history. It ensures systematic diagnosis rather than relying on ad-hoc investigation.

No, this bug resolution process does not require specific dependencies or external components to function. It provides a self-contained reasoning workflow that guides input normalization, reproduction, RCA, and verification across your software engineering tasks.