code-reviewlisted

# Code Review General correctness and maintainability review, and the entry point for the review suite. Detects what languages are in scope, delegates to the language reviewers that apply, and merges everything into one list under one rubric. For a threat-oriented pass — authentication, injection, secrets, crypto — use `security-review` instead. The two are complements, not substitutes: this skill asks "is this correct?", that one asks "can this be attacked?". ## Procedure Follow `../../references/procedure.md` for scoping, probing and error handling. Specifically: 1. **Scope.** Prefer the working diff (`git diff --name-only HEAD`, or `<base>...HEAD` for a branch or PR) over the whole tree, unless the user asked for the tree. State which you used. 2. **Detect languages** across every file in scope, using the extension map in `../../references/procedure.md`. 3. **Delegate.** For each language present, run the matching skill — `review-go`, `review-bash`, `review-vue-ts`, `review-php` — including its capability probe and its full checklist. 4. **Run the general checklist below** over every file in scope. It applies to files a language skill already covered as well: the language checklists look for language-specific traps, this one looks for logic and lifecycle defects that no linter has an opinion about. 5. **Merge and score** per `../../references/rubric.md`. 6. **Emit both artifacts** — report, then agent prompt block. ## Delegation - **Several languages