wordpress-quality

Run PHPStan, PHP_CodeSniffer, and PHPUnit checks on WordPress projects.

8|2|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/morodomi/tdd-skills --skill wordpress-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wordpress-quality
Source: https://github.com/morodomi/tdd-skills/tree/main/plugins/tdd-wordpress/skills/wordpress-quality
Command: npx skills add https://github.com/morodomi/tdd-skills --skill wordpress-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WordPress projects often struggle to maintain consistent quality due to inconsistent testing and standards enforcement. This skill provides automated quality checks using PHPStan, PHP_CodeSniffer with WordPress rules, and PHPUnit to catch issues early.

Core Features & Use Cases

  • Static analysis tailored for WordPress: PHPStan WordPress rules and custom checks.
  • Coding standards enforcement via WPCS: WordPress coding standards.
  • WordPress-specific tests: PHPUnit suites covering common WP patterns (hooks, REST, CPT).
  • Use Case: Integrate into CI to enforce quality gates before merges.

Quick Start

Install and configure PHPStan, PHP_CodeSniffer (WordPress standard), and PHPUnit in your project, then run the quality checks as part of your development workflow.

Frequently Asked Questions about wordpress-quality

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

FAQPage Schema
How do I enforce WordPress coding standards and run PHPStan in my project?

WordPress coding standards are enforced by running PHP_CodeSniffer with WPCS rules alongside PHPStan for static analysis. This combination detects violations and functional regressions during development and CI workflows.

What is the best way to automate WordPress quality checks in CI pipelines?

The best way to automate WordPress quality checks in CI is by running PHPStan, PHP_CodeSniffer with WordPress standards, and PHPUnit as quality gates before merges. This catches coding standard violations and functional regressions early.

Do I need to install PHPUnit and PHPStan separately before running WordPress quality checks?

Yes, you need PHPUnit, PHPStan, and PHP_CodeSniffer with WordPress standards installed in your project. These tools must be set up within a supported PHP environment before the quality checks can execute.

Can I use this quality checking approach with a Bedrock WordPress project?

Yes, these quality checks explicitly target WordPress and Bedrock projects. Running PHPStan, PHP_CodeSniffer, and PHPUnit validates code quality and catches regressions within Bedrock development and CI environments.

Why does my WordPress quality check fail on functional regressions during development?

WordPress quality checks fail on functional regressions when PHPUnit detects broken patterns in hooks, REST endpoints, or custom post types. Running PHPUnit suites identifies these issues before code merges.