Skip to content
lint logo

Lint

lint

Run formatting, linting, and type checking. Auto-detects project languages (Python, JS/TS, Bash). Fixes auto-fixable issues and stages changes.

SKILL.md

Full skill instructions

Lint

Auto-detects project languages and runs the appropriate formatting, linting, and type checking tools.

Usage

/​lint
/​lint --fix
/​lint backend
/​lint frontend

Behavior

1. Determine Scope

git diff --name-only HEAD
  • No argument: scope to changed files only
  • all: scope to the entire codebase (run tools without file args, e.g., ruff check src/ tests/, pyright, tsc --noEmit)
  • backend or frontend: scope to that workspace

2. Detect Project Languages

Check for these files in the project root (or relevant subdirectory):

IndicatorLanguageTools
pyproject.toml, setup.py, setup.cfg, *.py in diffPythonruff, pyright
package.json, tsconfig.json, *.ts/*.tsx/*.js/*.jsx in diffJS/​TSprettier, eslint, tsc
*.sh in diffBashshellcheck

Run only the tools that apply. If a tool isn't installed, ask the user if they want to install it via AskUserQuestion.

3. Python

Linting (Ruff):

# Check only
ruff check <changed-py-files>

# If --fix passed
ruff check --fix <changed-py-files>

Formatting (Ruff):

# Check only
ruff format --check <changed-py-files>

# If --fix passed
ruff format <changed-py-files>

If the project uses uv, prefix with uv run (check for uv.lock or project CLAUDE.md instructions).

Stage any fixes:

git add <fixed-files>

Type checking (Pyright):

pyright <changed-py-files>

Or uv run pyright if the project uses uv. Report type errors.

4. JavaScript / TypeScript

Formatting (Prettier):

npx prettier --check <changed-js-ts-files>

If --fix:

npx prettier --write <changed-js-ts-files>

Stage any fixes.

Linting (ESLint):

npx eslint <changed-js-ts-files>

If lint errors, attempt auto-fix:

npx eslint --fix <changed-js-ts-files>

Stage any fixes. Only lint files in the diff.

Type checking (TypeScript):

npx tsc --noEmit --pretty 2>&1

Report type errors.

5. Bash

Linting (shellcheck):

shellcheck <changed-sh-files>

Report issues. shellcheck has no auto-fix mode -- report findings for manual review.

Output

## Lint Results

### Python
- Ruff: PASS / FIXED N files / FAIL (N remaining)
- Pyright: PASS / FAIL (N errors in changed files)

### JavaScript / TypeScript
- Prettier: PASS / FIXED N files / FAIL
- ESLint: PASS / FIXED N errors / FAIL (N remaining)
- TypeScript: PASS / FAIL (N errors in changed files)

### Bash
- shellcheck: PASS / FAIL (N warnings)

- Files staged: N
- Verdict: PASS / FAIL

Only include sections for detected languages.

Rules

  • Default scope: changed files only. With all scope: entire codebase.
  • Stage auto-fix changes so the user sees them.
  • Fix ALL type errors found in scope — not just "report" them.
  • Report everything — even if all checks pass, show the summary.
  • If a tool isn't installed, ask the user if they want to install it via AskUserQuestion.

More skills from Marshall-Hallenbeck

multi-model-review logo
Marshall-Hallenbeck/dot_files

multi-model-review

Run code review with 4 free OpenCode models in parallel, then have them peer-review each other to reach consensus findings.

5 0
View
codex-review logo
Marshall-Hallenbeck/dot_files

codex-review

Run Codex and Claude code reviews iteratively until both find no issues. Use after making changes and before committing.

5 0
View
create-pr logo
Marshall-Hallenbeck/dot_files

create-pr

Creates a pull request with proper formatting, running tests first and including a structured description.

5 0
View
commit logo
Marshall-Hallenbeck/dot_files

commit

Commit session changes only, or all changes if no session edits.

5 0
View
run-quality-gate logo
Marshall-Hallenbeck/dot_files

run-quality-gate

Run full quality gate: linting, type checks, unit tests, and integration tests — all in parallel.

5 0
View
complete-github-issue logo
Marshall-Hallenbeck/dot_files

complete-github-issue

Use when asked to work on, implement, or complete a GitHub issue — before writing any code, checks issue state, existing PRs, git history, and codebase to determine what work remains or if the issue is already resolved

5 0
View
brainstorming logo
Marshall-Hallenbeck/dot_files

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

5 0
View
fix-tests logo
Marshall-Hallenbeck/dot_files

fix-tests

Autonomous test-fix pipeline. Runs full suite, diagnoses each failure, fixes source code, and iterates until all tests pass. Asks the user when uncertain about intended behavior.

5 0
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View