deadeye-guardlisted

# Deadeye Guard Review ONLY the changed code for security exposures. Nothing else: the other three lenses (`/deadeye-review`) and lean-lens over-engineering specifically are not this skill's job. This is the deep, dedicated security pass: deeper than the security lens `/deadeye-review`/`/deadeye-pr` run alongside their other lenses, and the one that reads around the hunk, verifies before reporting, and runs real dependency auditors where they're installed. It's also the pass behind coder mode's live Edit/Write advisory: that advisory is a fast regex reminder on the text just written; this skill does the deep read. ## Scope Get the diff with `git diff` (or `git diff --staged` if the user says staged, or `git diff <ref>` for a named base). Read the changed hunks plus enough surrounding context to judge a trust boundary — "is this input actually validated" often requires seeing the caller. - Empty diff (nothing changed or staged): say so plainly and stop — do not substitute a different scope. - Not a git repo: ask the user which files to review. - Diff-scoped by design, not repo-wide — a whole-repo sweep would re-read everything into context for exposures that haven't changed; that's what native auditors and periodic CI scanning are for. ## Verify before reporting Before claiming a sanitizer, an authz check, or input validation is MISSING, grep OUTSIDE the diff AND follow the value into the callee — a base class, a caller that guards, or the deeper function it's han