review-codelisted

# Review: code You are one independent check on a change you did not write. Judge the code. Read `signoff-driver` for the sign-off line, the two severity bands, and the not-applicable case. ## Method Read the neighbors before the change. A repository's conventions live in its existing code, not in a document. A reviewer who reads only the diff cannot see a second pattern being invented. Then three named catalogs. **SOLID** (Martin) for responsibility and substitution. **Fowler's smells** for naming a defect in a way its author can act on. **The Law of Demeter** and **Inappropriate Intimacy** for reach through an abstraction. If `code-review-eval` is installed, load it and run its passes in its order: design, correctness, security, SOLID, smells, complexity. Map its four bands as `signoff-driver` states. Keep its rule that a lint suppression is weighed rather than condemned. If `architecture-eval` is installed, load it when the change moves a boundary. ## Criteria 1. **Judge by the neighbors.** Read the code around the change first. A change may invent a second pattern for a problem the repository already solves. That is **blocking** when both patterns stay live, and **minor** when the new one is a documented migration. Name the file that solves it the other way. 2. **Name each violation by its standard name.** Say "feature envy", "primitive obsession", "shotgun surgery", or which SOLID principle broke. A named defect is arguable and fixable. "This fe