wp-phpstan

Use this skill when working on PHPStan in a WordPress codebase, for example: Prefer the repo’s existing composer script (e.g. composer run phpstan ) when present. szepeviktor/phpstan-wordpress or php-stubs/wordpress-stubs are effectively required for most WordPress plugin/theme repos. Without it, expect a high volume of errors about unknown WordPress core functions. See: Prefer correcting types over ignoring errors. Common WP patterns that need help: See: When integrating with plugins/themes not present in the analysis environment: See: See: - setting up or updating phpstan.neon / phpstan.neon.dist - generating or updating phpstan-baseline.neon - fixing PHPStan errors via WordPress-friendly PHPDoc (REST requests, hooks, query results) - handling third-party plugin/theme classes safely (stubs/autoload/targeted ignores) - wp-project-triage output (run first if you haven't) - Whether adding/updating Composer dev dependencies is allowed (stubs). - Whether changing the baseline is allowed for this task. - Inspect PHPStan setup (config, baseline, scripts): - node skills/wp-phpstan/scripts/phpstan_inspect.mjs - Confirm the package is installed (see composer.dependencies in the inspect report). - Ensure the PHPStan config references the stubs (see references/third-party-classes.md ). - Keep paths focused on first-party code (plugin/theme directories).