linting-workflow-skill

What I do

I provide a generic linting workflow for multiple languages:

• Detect project language and linter configuration
• Run linting and apply auto-fix when available
• Guide resolution of linting errors
• Verify fixes and commit changes

When to use me

Use when:

• Linting code before committing or PRs
• Building workflow skills with code quality checks
• Need consistent linting across multiple languages

This is a framework skill - provides linting logic that other skills extend.

Steps

Step 1: Detect Language and Linter

Detection:

• package.json + tsconfig.json → TypeScript (ESLint)
• package.json → JavaScript (ESLint)
• pyproject.toml / requirements.txt → Python (Ruff)
• go.mod → Go (golint/golangci-lint)
• Gemfile → Ruby (RuboCop)

Configuration files:

• ESLint: eslint.config.ts/js/mjs, .eslintrc.json/js/yaml
• Ruff: pyproject.toml, .ruff.toml, ruff.toml

Step 2: Detect Package Manager

Language	Manager	Lock File	Command
JS/TS	npm	package-lock.json	npm run <script>
JS/TS	yarn	yarn.lock	yarn <script>
JS/TS	pnpm	pnpm-lock.yaml	pnpm run <script>
Python	Poetry	pyproject.toml	poetry run <script>
Python	pip	requirements.txt	Direct command

Step 3: Run Linting

Commands:

# JavaScript/TypeScript (ESLint)
npm run lint              # npm
yarn lint                 # yarn
pnpm run lint            # pnpm
npx eslint .             # direct

# Python (Ruff)
ruff check .             # direct
poetry run ruff check .  # poetry

Step 4: Apply Auto-Fix

Auto-fix commands:

• ESLint: npm run lint -- --fix
• Prettier: npx prettier --write .
• Ruff: ruff check . --fix
• Black: black .

Auto-fix capabilities:

• Style violations, unused variables, simple syntax issues
• Formatting, indentation, quotes
• Unused imports, simple refactorings

Step 5: Fix Remaining Errors