run-linters
Run Project Linters
When asked to run linters, check code quality, or verify changes:
1. Discover Available Linters
Check for configuration files to determine which linters are available:
PHP Linting
phpcs.xmlorphpcs.xml.dist→ PHPCS availablephpstan.neonorphpstan.neon.dist→ PHPStan available
JavaScript Linting
.eslintrc.*oreslint.config.*→ ESLint available
CSS/SCSS Linting
.stylelintrc*→ Stylelint available
2. Check for Lint Scripts
More from humanmade/claude-code-standards
css-scss-human-made
Human Made CSS and SCSS standards. Apply when writing styles, reviewing CSS/SCSS, or working on theme styling. Covers BEM naming, CSS custom properties, theme.json integration, and Stylelint configuration.
20react-human-made
Human Made React component standards. Apply when writing React components, reviewing React code, or building WordPress block editor interfaces. Covers functional components, hooks, PropTypes, and component organization.
1php-human-made
Human Made PHP coding standards for WordPress development. Apply when writing PHP, reviewing PHP code, or working on WordPress plugins and themes. Covers PHPCS HM-Minimum ruleset, namespacing conventions, bootstrap patterns, type hints, and file organization.
1javascript-human-made
Human Made JavaScript coding standards. Apply when writing JavaScript or TypeScript, reviewing JS code, or working on frontend features. Covers ES6+ conventions, modern patterns, and ESLint configuration.
1hm-coding-philosophy
Human Made engineering principles and code quality standards. Apply when writing code, reviewing code, planning implementations, or discussing architecture. Covers code quality priorities, simplicity over complexity, and avoiding over-engineering.
1