Configure, run, or fix PHPStan in WordPress codebases (plugins/themes/sites). Use whenever creating or editing phpstan.neon / phpstan.neon.dist, generating or shrinking phpstan-baseline.neon, raising/lowering level:, fixing PHPStan errors with WordPress-friendly PHPDoc (WPRESTRequest , hook-callback @param types, array shapes for $wpdb results, Action Scheduler $args shapes), wiring up szepeviktor/phpstan-wordpress or php-stubs/wordpress-stubs, adding plugin-specific stubs (php-stubs/woocommerce-stubs, php-stubs/acf-pro-stubs), narrowing paths / excludePaths, or scoping ignoreErrors patterns to a vendor prefix. Trigger on any mention of phpstan, neon config, static analysis in PHP, @phpstan- annotations, baseline file growth, 'class not found' errors after enabling phpstan, or 'how do I type a WP hook callback'. Pair with wordpress-project-triage first to know which paths to analyse. Don't use for PHPCS / WordPress Coding Standards (different tool).
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
Configure, run, or fix PHPStan in WordPress codebases (plugins/themes/sites). Use whenever creating or editing phpstan.neon / phpstan.neon.dist, generating or shrinking phpstan-baseline.neon, raising/lowering level:, fixing PHPStan errors with WordPress-friendly PHPDoc (WPRESTRequest , hook-callback @param types, array shapes for $wpdb results, Action Scheduler $args shapes), wiring up szepeviktor/phpstan-wordpress or php-stubs/wordpress-stubs, adding plugin-specific stubs (php-stubs/woocommerce-stubs, php-stubs/acf-pro-stubs), narrowing paths / excludePaths, or scoping ignoreErrors patterns to a vendor prefix. Trigger on any mention of phpstan, neon config, static analysis in PHP, @phpstan- annotations, baseline file growth, 'class not found' errors after enabling phpstan, or 'how do I type a WP hook callback'. Pair with wordpress-project-triage first to know which paths to analyse. Don't use for PHPCS / WordPress Coding Standards (different tool).
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Configure, run, or fix PHPStan in WordPress codebases (plugins/themes/sites). Use whenever creating or editing `phpstan.neon` / `phpstan.neon.dist`, generating or shrinking `phpstan-baseline.neon`, raising/lowering `level:`, fixing PHPStan errors with WordPress-friendly PHPDoc (`WP_REST_Request<...>`, hook-callback `@param` types, array shapes for `$wpdb` results, Action Scheduler `$args` shapes), wiring up `szepeviktor/phpstan-wordpress` or `php-stubs/wordpress-stubs`, adding plugin-specific stubs (`php-stubs/woocommerce-stubs`, `php-stubs/acf-pro-stubs`), narrowing `paths` / `excludePaths`, or scoping `ignoreErrors` patterns to a vendor prefix. Trigger on any mention of phpstan, neon config, static analysis in PHP, `@phpstan-` annotations, baseline file growth, 'class not found' errors after enabling phpstan, or 'how do I type a WP hook callback'. Pair with `wordpress-project-triage` first to know which paths to analyse. Don't use for PHPCS / WordPress Coding Standards (different tool).
About this listing
Category
Engineering
Reported license
Not specified
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.