Lint

automattic/lint

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

233 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

150

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Automattic/vip-go-mu-plugins-built --skill lint

The instruction itself

3 sections, as written by the author

Lint

Run after editing files. Fix all issues before finishing.

Commands

# 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

Run PHP format first (composer format)
Run PHP lint to verify (composer lint)
Run PHPStan (composer analyze)
Run JS/CSS lint if frontend files changed (npm run lint)
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.

How to use it

Copy the folder

Take automattic/lint from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.