What problem does it solve? Large refactors in C#/.NET and TypeScript/Angular projects often produce hundreds of build errors and test failures at once. Blindly applying global find-and-replace in this situation breaks contexts you haven't examined and causes cascading regressions. This Skill provides a disciplined triage workflow for safely working through high-volume post-refactor breakage. ## Core Features & Use Cases - Error categorization workflow: Group compiler errors by code and symbol (e.g., CS0117, CS1503, CS0246), hypothesize root causes per category, and present the analysis to the user before fixing anything. - Category-by-category fixing: Fix one error category at a time, verifying with dotnet build that counts drop by exactly the expected amount after each pass. - Pitfall library: 28+ documented C# pitfalls (record private init, nameof(T) on generics, JSON camelCase serialization, NSubstitute expression-tree limits, stale --no-build binaries) plus Angular/TypeScript pitfalls (vitest setup, package.json duplicate keys, SPA rewrites). - Use Case: After renaming a domain type across a .NET solution, you face 365 build errors. Use this Skill to group them into ~8 root-cause categories, confirm the plan with the user, then fix each category with verified incremental builds. ## Quick Start Ask the AI to triage and fix the build errors from your recent refactor using the refactoring-fix approach, starting with categorizing errors by code and symbol before making any changes.
