code-quality

Review WordPress code against WPCS standards and static analysis tools.

27|1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dr-robert-li/cowork-wordpress-expert --skill code-quality-dr-robert-li
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/dr-robert-li/cowork-wordpress-expert/tree/main/skills/code-quality
Command: npx skills add https://github.com/dr-robert-li/cowork-wordpress-expert --skill code-quality-dr-robert-li

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires wp-coding-standards/wpcs, phpstan/phpstan, szepeviktor/phpstan-wordpress, vimeo/psalm, @wordpress/eslint-plugin, stylelint-config-wordpress, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for high-quality, maintainable, and standards-compliant WordPress code by providing automated checks for coding standards, static analysis, architectural patterns, and error handling.

Core Features & Use Cases

  • Coding Standards Enforcement: Verifies adherence to WordPress PHP, JavaScript, CSS, and HTML coding standards.
  • Static Analysis: Utilizes tools like PHPCS, PHPStan, Psalm, and ESLint to detect bugs, vulnerabilities, and code smells.
  • Architecture Review: Assesses the use of WordPress hooks, namespacing, autoloading, and separation of concerns.
  • Error Handling Validation: Checks for graceful error management and the use of WordPress error patterns.
  • Deprecated Function Detection: Identifies the use of outdated or removed functions.
  • Use Case: Before deploying a custom plugin or theme, use this Skill to perform a comprehensive code audit, ensuring it meets WordPress best practices and is free from common pitfalls.

Quick Start

Run a full code quality analysis on the /path/to/your/wordpress/plugin directory.

Frequently Asked Questions about code-quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my WordPress plugin against WPCS coding standards?

To check a WordPress plugin against WPCS coding standards, this Skill reviews custom themes and plugins using PHPCS to verify adherence to WordPress PHP, JavaScript, CSS, and HTML coding conventions.

Can I run PHPStan and Psalm static analysis on WordPress themes?

Yes, you can run static analysis on WordPress themes using PHPStan and Psalm to detect bugs, vulnerabilities, and code smells alongside PHPCS and ESLint for comprehensive code validation.

Do I need ESLint and Stylelint configured for WordPress code review?

Yes, you need ESLint with the WordPress plugin and Stylelint configured to perform comprehensive code validation across JavaScript and CSS files during your WordPress code review.

What's the best way to detect deprecated WordPress functions in my codebase?

The best way to detect deprecated WordPress functions in your codebase is to use this Skill to perform a comprehensive code audit, identifying outdated or removed functions before deployment.

How does WordPress architecture review handle hooks and autoloading?

WordPress architecture review handles hooks and autoloading by assessing the use of WordPress hooks, namespacing, autoloading, and separation of concerns to ensure maintainable code structure.

Why does my WordPress static analysis fail to catch architectural issues?

Standard static analysis fails to catch architectural issues because it focuses on bugs; this Skill augments PHPStan and PHPCS by explicitly assessing WordPress hooks, namespacing, and separation of concerns.