What killed your codebase?

First on the scene. Secures the perimeter, locks down the commit, and preps the case file before the specialists arrive.

Unravels functions whose branching and nesting read like a confession written in mirror writing. Separates real complexity hotspots from harmless structure.

Tracks down god objects, mile-long methods, and bloated workflow files. Finds the places where one file is doing six jobs and dropping all of them.

Listens for the telltale echo of duplicated logic: parallel helpers, lookalike abstractions, and homemade mini-frameworks that scatter every future change.

Investigates suspicious silences. Empty catch blocks, broad excepts, and log-and-continue paths - anywhere a failure was quietly buried instead of handled.

Walks the morgue. Identifies unused declarations, generated-code residue, one-call abstractions, and other deceased citizens still on the books.

Cross-examines the test suite. Flags missing assertions, tautologies, constant-truth checks, and shallow snapshots - the fake alibis that pass without proving a thing.

Reads between the lines. Flags comments that restate syntax, miss the tradeoffs, or paper over the real reason the code looks like that.

Reviews every detective's notes, dedupes evidence, runs a final secrets sweep, and signs off on the audit report and scorecard.