code-quality-guidelisted

# Code-Quality Audit A read-only pass over existing code: find smells, grade them by severity, report, and route each smell to the one skill that owns its definition and fix. It changes nothing. ## Essentials - **Read the project's own standards first**: `AGENTS.md` / `POLICY.md` / linked guidelines and the linter config decide what counts as a violation, not generic best-practice - **Robustness is this skill's own dimension**: type safety, validation, error handling, logging at boundaries, complexity, see [references/robustness.md](references/robustness.md) - **Route every other smell to its owner**: the catalog maps each smell to a detector signal and the skill that owns it, see [references/smell-catalog.md](references/smell-catalog.md) - **Keep cleanup inventories read-only**: preserve functional comments and rationale; detect prose debt and other cleanup candidates, see [references/comment-inventory.md](references/comment-inventory.md) and [references/cleanup-inventories.md](references/cleanup-inventories.md) ## Gotchas - This skill is a read-only **detector and grader**. It names a smell and routes to the owner (**oop-guide** for OO-design smells, **connascence-guide** for coupling smells); it does not redefine or fix them. - "Dead code" detection misses code reached via dynamic dispatch, reflection, or external entry points: verify before flagging for deletion. - A single-implementation interface is not automatically over-engineering. It may exist for testability o