Skip to content
TrustedSkillsbeta
Back to all skills

Wp Phpstan

Official
automattic·vlatest·backend

Wp Phpstan analyzes WordPress code for potential errors and style issues, boosting code quality and preventing bugs during development.

Repository

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 automattic/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

automattic

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 automattic/agent-skills at 48d4aa21d0.

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

Commit
48d4aa21d0
Manifest
skills/wp-phpstan/SKILL.md
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 codebases for potential errors and style issues using PHPStan, a static analysis tool. It helps developers improve code quality, prevent bugs, and maintain a consistent coding standard within WordPress projects. The skill assists with configuring PHPStan specifically for WordPress development, including handling core functions and third-party plugin/theme integrations.

When to use it

  • 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, especially for REST requests, hooks, and database query results.
  • Safely handling code from third-party plugins and themes using stubs or targeted ignores.
  • Managing baseline files to address legacy code issues over time.

Key capabilities

  • Discovers PHPStan entrypoints automatically.
  • Ensures WordPress core stubs (like szepeviktor/phpstan-wordpress or php-stubs/wordpress-stubs) are loaded for accurate analysis.
  • Helps configure a suitable phpstan.neon file, focusing on first-party code and excluding unnecessary files like vendor directories.
  • Provides guidance on correcting types in WordPress-specific code patterns (REST endpoints, hook callbacks, database results).
  • Offers strategies for handling third-party plugin/theme classes through stubs or targeted error ignores.

Example prompts

  • "Analyze this WordPress plugin's code with PHPStan and update the phpstan.neon file."
  • "Generate a baseline file for my WordPress theme to address existing errors."
  • "Help me fix the PHPStan errors related to REST API request parameters in this function."

Tips & gotchas

  • The skill requires a "wp-project-triage" output as initial input.
  • Ensure WordPress core stubs are installed and properly configured within the phpstan.neon file for accurate results; otherwise, expect numerous errors related to unknown functions.
  • Prioritize correcting code types over simply ignoring PHPStan errors whenever possible.