rigor-unused-adjudicate

Adjudicating rigor unused

rigor unused answers which project classes and modules does no reachable code name? — not what can I delete. Closing that gap is the work, and the manual chapter has the method:

rigor docs 18-removing-dead-code

Read it before adjudicating anything. It carries the false-positive shapes with their measured frequencies, the pre-deletion checklist, and how to report the result. This skill exists for the part the chapter cannot do for you: work out what the report can and cannot see on this particular project, before you trust a single row.

Do that first, because every check below changes how the output should be read — and skipping one is how a live class ends up on a deletion list.

Establish the ground first

Run the report and answer these against the project in front of you.

Are framework roots actually supplied? When a plugin contributes roots, the summary's roots: line grows a parenthetical: roots: N (M from plugins, K matched no declaration). The parenthetical is omitted entirely when no plugin contributed — so on a framework application, a bare roots: N with no (… from plugins …) note means nothing is naming your controllers, jobs or policies, and most of the report is noise. Stop and fix the plugin configuration — rigor docs 07-plugins — rather than adjudicating hundreds of rows.

Does the project ship signatures? If signature_paths: is configured, also run with it emptied and compare:

rigor unused                            # normal
rigor unused --config /tmp/no-sig.yml   # a copy of your config with signature_paths: []

Adjudicate the union. On one application the signature-free run surfaced three genuinely dead classes that the default run never showed. Rows that appear only without signatures are still worth checking — signatures reference classes, and a reference the report counts is not always one a human would.

What do paths: actually cover? Only Ruby under those paths is analysed. Views are the common gap: a helper called from app/views/**/*.erb has no Ruby caller at all, and will land in the report looking unused. Before believing any helper or presenter row, grep the view tree for it.