code-audit-deeplisted

# Code Audit (Deep) Line-level audit. Companion to `architectural-hotspots`. Hotspots ranks files by structural shape (fan-in, fan-out, LOC, cycles); this skill reads files and emits specific, actionable findings with line numbers and fix sketches. The core failure mode this skill exists to prevent: producing vague "consider refactoring X" advice instead of `commit.rs:426 — clock sampled per element in hot loop; hoist or seed-and-increment`. The first is what a graph tool already said; the second is what the user actually wanted. ## Language scope This skill is **language-agnostic**. The smells below are concepts that recur across stacks; the parenthetical examples are illustrative for a few common languages but never exhaustive. When you read a file, map each smell to the *equivalent* construct in the target language: - "fallible call return value discarded" covers `let _ = f()` (Rust), bare `f()` ignoring its `error` return (Go), `try: f(); except: pass` (Python), unawaited `f()` returning a Promise (TS / JS), `_, _ = f()` patterns (Lua / Go), `f(); // ignore` everywhere. - "owned-when-borrow-suffices" covers `Vec<String>` vs `Vec<&str>` (Rust), `[]string` copies vs slice aliases (Go), deep-copying lists (Python), `.slice()` cloning vs index access (JS), `std::string` vs `std::string_view` (C++). - "lock-when-atomic-suffices" covers `Arc<Mutex<u64>>` (Rust), `sync.Mutex` for a counter (Go), `threading.Lock` around an int (Python), `Object.synchronized` f