← ClaudeAtlas

review-toolinglisted

Detect what dev tooling infrastructure a project has and flag gaps across linters, formatters, pre-commit hooks, test runners, and CI/CD pipelines. Returns structured findings without applying changes. Use when the user asks to "review tooling", "check project tooling", "what tooling is missing", "review dev infrastructure", or "tooling audit".
tobihagemann/turbo · ★ 419 · Code & Development · score 89
Install: claude install-skill tobihagemann/turbo
# Review Tooling Detect dev tooling infrastructure and flag gaps. Analysis only. Does not install or configure tools. ## Scope Tooling review always operates at the project level since config files live at the project root. Scope parameters (diff commands, file lists) are accepted but ignored. When called standalone, use the git repository root as the project root (fall back to the current working directory if not in a git repo). ## Step 1: Detect Tooling Search for config files in the project root and subdirectories (exclude vendored directories like `node_modules/`, `vendor/`, `.build/`). Classify findings into five categories: ### Linters | Config file pattern | Tool | |---|---| | `.eslintrc*`, `eslint.config.*` | ESLint | | `biome.json`, `biome.jsonc` | Biome (linter + formatter) | | `deno.json`, `deno.jsonc` with `lint` config | Deno lint | | `.swiftlint.yml` | SwiftLint | | `ruff.toml`, `[tool.ruff]` in `pyproject.toml` | Ruff | | `.pylintrc`, `pylintrc` | Pylint | | `.flake8`, `[flake8]` in `setup.cfg` | Flake8 | | `.rubocop.yml` | RuboCop | | `.golangci.yml`, `.golangci.yaml` | golangci-lint | | `clippy.toml`, `.clippy.toml` | Clippy | | `ktlint*`, `.editorconfig` with `ktlint` | ktlint | ### Formatters | Config file pattern | Tool | |---|---| | `.prettierrc*`, `prettier.config.*` | Prettier | | `biome.json`, `biome.jsonc` | Biome (linter + formatter) | | `deno.json`, `deno.jsonc` with `fmt` config | Deno fmt | | `.swift-format`, `.swiftformat` | swift-forma