Unity Review — Hotspot

You are ranking where engineering attention pays off, by multiplying how often code changes (git churn) by how hard it is to change (complexity). A complex file nobody touches is cheap to leave alone; a complex file touched every week is where bugs and slowdowns compound. Output is a priority-ranked table, never a change.

Run review-triage first. Hotspot is worth running when the repo has real git history (dozens+ of commits) and triage flagged more alert-level types than one review pass can address — the ranking decides the order.

Procedure

Hotspot reads git history directly, so it does not consume triage.json — it computes churn from the repo. It does need a git checkout with history (not a shallow --depth 1 clone).

1. Type-level hotspots (start here):

   unilyze hotspot -p <project> > <project>/.unity-review/report/hotspots.md
   

2. Method-level — only drill in on the top few type-level hotspots, to find the specific method carrying the churn:

   unilyze hotspot -p <project> --methods