Skip to content
TrustedSkillsbeta
Back to all skills

Wp Phpstan

Official
wordpress·vlatest·backend

WP PHPStan analyzes WordPress code for potential errors and style issues, boosting code quality and preventing bugs.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add wordpress/agent-skills --skill wp-phpstan -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

wordpress

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned wordpress/agent-skills at 3cf7f6f701.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
5 files, 595 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The WP PHPStan skill analyzes WordPress code for potential errors and style issues using PHPStan, a static analysis tool. It helps improve code quality by identifying bugs and inconsistencies within WordPress projects, particularly plugins and themes. The skill guides users through configuring and running PHPStan effectively in a WordPress environment, including handling WordPress-specific coding patterns and third-party dependencies.

When to use it

This skill is useful when:

  • Setting up or updating the phpstan.neon or phpstan.neon.dist configuration files.
  • Generating or updating the phpstan-baseline.neon file.
  • Fixing PHPStan errors by improving PHPDoc comments to reflect WordPress patterns (e.g., REST requests, hooks, query results).
  • Safely handling classes from third-party plugins and themes using stubs or targeted ignores.
  • Managing the baseline file as a tool for migrating legacy code towards better quality.

Key capabilities

  • Discovers PHPStan entrypoints automatically.
  • Inspects existing PHPStan configurations (config, baseline, scripts).
  • Ensures WordPress core stubs are loaded (szepeviktor/phpstan-wordpress or php-stubs/wordpress-stubs).
  • Guides users on creating a suitable phpstan.neon configuration for WordPress projects.
  • Provides guidance on fixing errors using WordPress-specific typing and PHPDoc annotations.
  • Offers strategies for handling third-party plugin/theme classes when stubs are unavailable.
  • Manages baseline files to track and reduce legacy code issues.

Example prompts

  • "Analyze my WordPress plugin's code with PHPStan."
  • "Generate a baseline file for my WordPress theme."
  • "Help me fix the PHPStan errors related to REST endpoints in my plugin."

Tips & gotchas

  • The skill requires a wp-project-triage output as input. Run this first if you haven't already.
  • Ensure that WordPress core stubs are loaded, otherwise expect numerous errors about unknown functions.
  • Prioritize correcting types and improving PHPDoc over simply ignoring PHPStan errors.