code-linting

# Code Linting Skill Unified linting workflow for Python (ruff) and JavaScript (Biome). Covers check, format, and auto-fix for both languages. Only handles Python and JavaScript/TypeScript -- complex logic issues and other languages are out of scope. ## Reference Loading Table | Signal | Load These Files | Why | |---|---|---| | Python violations, ruff rules, F401/E711/B006/UP errors | `ruff-rules-reference.md` | Routes to the matching deep reference | | ruff not found, pyproject.toml config, ruff version differences | `ruff-rules-reference.md` | Routes to the matching deep reference | | JavaScript/TypeScript violations, Biome rules, noVar/useConst/noDoubleEquals | `biome-rules-reference.md` | Routes to the matching deep reference | | biome not found, biome.json config, migrating from ESLint | `biome-rules-reference.md` | Routes to the matching deep reference | | Linting CI failures, format check vs lint check differences | `biome-rules-reference.md` | Routes to the matching deep reference | ## Instructions ### 1. Read Project Configuration Before running any linter, read the repository's CLAUDE.md for project-specific linting rules -- those override every default below. Then locate the project's linter config files (`pyproject.toml` for ruff, `biome.json` for Biome). All linter invocations must use these configs as-is; never override line width, rule sets, or other project settings. ### 2. Detect Languages and Run Checks When a project contains both Python and JavaScr...