Reviewing PL/SQL

Announce at start: "Using plsql-review — checking the database's signals first."

Review in two passes: what the database knows is wrong, then what the checklist says is likely wrong. Machine signals first — they are free and exact.

Pass 1 — the database's own verdict

1. pythia errors NAME — compile errors and warnings with line:column. An object that does not compile needs no style review yet.
2. pythia src NAME — read the source with the compiler's line numbers, so findings can be anchored (line 47: ...).
3. pythia impact NAME --depth 2 — how exposed is this object; a finding in something with 40 dependents outranks the same finding in a leaf.
4. For a proposed file (not yet applied): the compile verdict arrives at apply time — say explicitly that compilation is still unverified.