exception-audit

To audit exception handling, load your solution into a Roslyn workspace and run the audit to identify catch blocks, classify their patterns, and generate a ranked report of unhandled-at-boundary throw sites and swallow risks.

An exception swallow risk in C# code quality analysis is a catch block that silently absorbs errors without rethrowing or handling them, which this audit identifies by classifying catch-body patterns to surface hidden boundary risks.

Yes, you can filter the exception audit to specific types. The audit covers all exceptions in scope or an optional filter, categorizing reachable catch clauses and flagging unhandled-at-boundary throw sites for targeted refactoring.

Yes, the exception audit works with a loaded Roslyn workspace. It relies on Roslyn MCP tools like trace_exception_flow, symbol_search, and analyze_control_flow to extract, analyze, and rank catch-body patterns across the solution.

The best way to find overly broad catch blocks in C# is to run a solution-wide audit that uses Roslyn control flow analysis to identify and classify all catch clauses, producing a ranked report to guide targeted refactors.

You should use a Roslyn-based exception flow analysis when you need a repo-wide classification of exception handling patterns in large codebases to identify unhandled-at-boundary throw sites and improve error-handling practices.