requesting-code-reviewlisted

# Requesting Code Review Before another set of eyes — yours or a reviewer's — do the cheap pass yourself. Self-review catches 60% of issues without burning anyone else's attention. ## When to run this - Before `git commit` - Before opening a PR - Before handing work off to another agent / human - Before invoking the `code-reviewer` subagent (don't waste its budget on lint issues) ## Iron Law **Read your own diff before anyone else does.** Open the diff, scroll top-to-bottom, every line. No skipping. ## Self-Review Checklist ### Correctness - [ ] Tests pass (see [[verification-before-completion]] — don't assume) - [ ] The change actually does what the task asked - [ ] Edge cases handled: empty input, null, zero, negative, very large, unicode - [ ] Error paths considered — not just the happy path ### Cleanliness - [ ] No `print` / `console.log` / `Write-Host` debug statements left behind - [ ] No commented-out code blocks ("might need later" — no, delete it, git remembers) - [ ] No TODOs added without a ticket / follow-up - [ ] No dead code (unreachable branches, unused imports/vars) ### Naming & Clarity - [ ] Variable / function names communicate intent, not type (`userList` not `arr`) - [ ] No abbreviations only you understand - [ ] Functions do one thing; if a name needs "and", split it ### DRY / Reuse - [ ] Not duplicating an existing helper — searched the codebase first - [ ] If duplicating intentionally (different abstraction), noted why - [ ] Not introducing a