← ClaudeAtlas

code-qualitylisted

ESLint, Prettier, Ruff, mypy, and TypeScript strict mode configuration patterns. Use when setting up linting, formatting, or code quality tooling for a new project, reviewing existing configs, generating config files, or adding lint steps to CI. Triggers on tasks involving ESLint, Prettier, Ruff, mypy, Black, code style, linting, formatting, or code quality enforcement.
Brite-Nites/brite-claude-plugins · ★ 0 · Code & Development · score 63
Install: claude install-skill Brite-Nites/brite-claude-plugins
# Code Quality Enforcement Canonical configuration patterns for JavaScript/TypeScript and Python code quality tooling. Auto-detect project type, generate config files, and integrate with CI. ## When to Use This Skill - Setting up linting and formatting for a new project - Reviewing or upgrading existing code quality configs - Generating ESLint, Prettier, Ruff, or mypy configuration files - Adding lint/format steps to GitHub Actions CI - Diagnosing why a linter isn't catching issues (wrong config, missing rules) - Migrating from legacy tooling (TSLint → ESLint, Black/flake8/isort → Ruff) ## Auto-Detection Identify the project stack from these markers before generating configs: | Marker file | Stack | Tools to configure | |---|---|---| | `package.json` | JavaScript/TypeScript | ESLint, Prettier | | `tsconfig.json` | TypeScript (additional) | TypeScript strict mode, `tsc --noEmit` | | `pyproject.toml` | Python | Ruff, mypy | | `setup.py` or `setup.cfg` | Python (legacy) | Ruff, mypy | | Both `package.json` + `pyproject.toml` | Full-stack | All of the above | When auto-detecting, check for existing configs first (`.eslintrc*`, `eslint.config.*`, `.prettierrc*`, `[tool.ruff]` in pyproject.toml) — upgrade rather than overwrite. --- ## JavaScript/TypeScript Stack ### ESLint (Flat Config — v9+) Use `eslint.config.mjs` (flat config). Legacy `.eslintrc.*` is deprecated as of ESLint v9. ```js // eslint.config.mjs import js from "@eslint/js"; import tseslint from "typescript-