bug-diagnosis

Stack trace diagnosis involves parsing error messages to identify the failure point, then tracing backward through the call chain to find the root cause. This Skill analyzes stack traces across both C# backend and Angular frontend layers, pinpointing which component failed and why, then guides you to the exact code location needing repair.

Effective runtime exception debugging requires systematically reproducing the error, examining logs and stack traces, forming hypotheses about the cause, and testing each hypothesis against evidence. This Skill structures that workflow across your .NET backend and Angular frontend, validating claims with code citations before suggesting fixes.

Yes. This Skill handles error interpretation and diagnosis across compile-time errors, runtime exceptions, failing tests, and degraded functionality. It applies the same evidence-based analysis method—stack trace parsing, semantic code reasoning, and structured validation—regardless of error type or symptom.

Regression risk assessment examines how a bug fix impacts other parts of your codebase. This Skill maps cross-service dependencies, traces function calls, and highlights which other components could be affected, helping you validate that your fix doesn't break existing functionality elsewhere in the application.

No. You can start with a stack trace or error message, and this Skill will guide discovery of relevant files. It performs structured file analysis and batch operations to locate the problematic code, then generates file lists and analysis notes for targeted investigation without requiring upfront submission of your entire project.