code-qualitylisted

# Purpose Scans specified TypeScript or Python source files and produces a scored report identifying functions exceeding length thresholds, deep nesting, duplicate code blocks, and project-specific anti-patterns (e.g., eager DB init, missing `force-dynamic`, missing `async`/`await`). The report assigns a 0-100 score per category and lists every finding with `file:line` citations. This skill owns **structural** quality: function length, cyclomatic complexity, nesting depth, code smells, and duplicate code. It does NOT own `any`-type detection, missing type annotations, or naming conventions -- those belong to `code-standards`. # When to use / When NOT to use **Use when:** - Someone asks you to audit a file or module for function length, complexity, nesting depth, or code smells - A PR needs a structural quality assessment (function size, duplication, nesting) - A periodic quality audit of a repository or module is requested - After a refactoring, to verify that structural quality metrics improved **Do NOT use when:** - Reviewing code for naming conventions, `any` types, import ordering, or style compliance (use `code-standards`) - Verifying that DB schema fields match validation schemas and route handlers (use `api-contract`) - Auditing deployment YAML or manifests (use `deployment`) - Listing files or navigating the codebase without quality assessment intent (use `code-search`) **Boundary with `code-standards`:** If the question is "does this code follow conventions?" r