code_review_selflisted

# code_review_self Writing code and reviewing code are different mental modes. Switching between them deliberately — even briefly — catches mistakes that you'd miss in the flow of writing. This skill is a structured checklist for reviewing your own code output before presenting it to the user. ## Why Self-Review Matters When writing code, you hold a mental model of what you intended. When reviewing, you should read what's actually there. These two things frequently differ. A second pass, even by the same author, catches: - Logic that made sense while writing but is actually wrong. - Edge cases that weren't handled. - Errors that are missing or swallowed silently. - Inconsistencies with the surrounding codebase. ## The Review Checklist ### 1. Correctness — Does it do what it's supposed to do? - [ ] Read the code as if you're seeing it for the first time. Does it do what the user asked? - [ ] Mentally trace through the happy path with a concrete example. Does the output match what you'd expect? - [ ] Trace through at least one error case. What happens if the input is None/null/empty/zero/negative? Does the code handle it, or does it crash? - [ ] If there are loops or recursion, is the termination condition correct? Any possibility of infinite loop or stack overflow? - [ ] If there's async code, are all awaits in place? Is there any accidentally-missed `await` that would return a coroutine instead of a value? ### 2. Completeness — Is anything missing? - [ ] Are all the e