# Lint

> Run linting, formatting, and type checking on changed files. Use when asked to "lint", "fix linting", "run linter", "check formatting", or "check types".

- Skill: `automattic/lint` (Agent Skill)
- Install (CLI): `npx skillmds@latest add automattic/lint`
- Raw SKILL.md: https://api.skillmd.com/api/skills/automattic/lint/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Automattic (https://skillmd.com/u/automattic)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/automattic/lint

---


# Lint

Run after editing files. Fix all issues before finishing.

## Commands

```bash
# PHP — auto-fix coding standards
composer format

# PHP — verify clean
composer lint

# PHP — static analysis (PHPStan level 6)
composer analyze

# JS — lint with auto-fix
npm run lint:js:fix

# CSS — lint with auto-fix
npm run lint:css:fix

# All JS/CSS linters
npm run lint
```

## Workflow

1. Run PHP format first (`composer format`)
2. Run PHP lint to verify (`composer lint`)
3. Run PHPStan (`composer analyze`)
4. Run JS/CSS lint if frontend files changed (`npm run lint`)
5. If any check fails, fix errors and re-run — don't push until clean.

If only PHP files changed, skip JS/CSS checks. If only JS/CSS files changed, skip PHP checks.