skills.rest
korflux
korfluxCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

wordpress-core-development

Route and validate WordPress Core changes in the wordpress-develop codebase.

Updated Aug 23, 2026
Search Tags:#validation#phpunit#wordpress#core-development#trac#wordpress-core#wordpress-develop
One-click install
npx skills add https://github.com/korflux/skills --skill wordpress-core-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wordpress-core-development
Source: https://github.com/korflux/skills/tree/main/skills/wordpress-core-development
Command: npx skills add https://github.com/korflux/skills --skill wordpress-core-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WordPress Core development tasks in the wordpress-develop codebase often lack a clear, surface-aware workflow, causing misrouting to Gutenberg or plugins and slowing contributor progress. This skill provides a structured, repo-aware approach that guides you from nearest implementation to core workflow, with an emphasis on proper routing, validation, and contributor context.

Core Features & Use Cases

  • Repo-aware routing: locate owning Core surface (wp-admin, wp-includes, bootstrap internals, REST API) and route work to the correct area.
  • Standardized validation: apply WordPress Core commands and testing surfaces (PHPUnit, PHPCS, PHPStan, Playwright as needed) to validate changes with minimal risk.
  • Contributor-ready workflow: align with Trac tickets and contribute context for patch reviews and integration.
  • Use Case: debugging a failing Core test in wordpress-develop and preparing a minimal, reviewer-friendly patch with nearby tests.

Quick Start

Review the wordpress-core-development workflow in wordpress-develop, locate the nearest implementation or test, and follow the standard Core validation steps.

Frequently Asked Questions about wordpress-core-development

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

FAQPage Schema
How do I route a bug fix to the correct WordPress Core surface instead of Gutenberg?▼

To route a WordPress Core bug fix correctly, identify the owning Core surface like wp-admin, wp-includes, or REST API in the wordpress-develop codebase. This ensures changes target Core rather than Gutenberg or plugins, preventing misrouting and slowing contributor progress.

What's the best way to validate WordPress Core patches before submitting a Trac ticket?▼

The best way to validate WordPress Core patches is by applying standard Core testing surfaces like PHPUnit, PHPCS, PHPStan, and Playwright. This targeted validation ensures minimal risk and aligns with repository-aware workflow standards for contributor-ready patches.

How do I prepare a minimal, reviewer-friendly patch for WordPress Core?▼

To prepare a minimal WordPress Core patch, locate the nearest implementation or test in the wordpress-develop repository, apply minimal patching, and run standard Core validation commands. This workflow produces reviewer-friendly patches aligned with Trac ticket context.

Does WordPress Core development require working within the wordpress-develop codebase?▼

Yes, WordPress Core development requires working within the wordpress-develop codebase to implement precise repository-aware changes. It provides the structured environment necessary for proper surface routing, component ownership decisions, and standardized validation.

When should I distinguish a WordPress Core change from a Gutenberg boundary decision?▼

You should distinguish a WordPress Core change from a Gutenberg boundary decision when the implementation touches wp-admin, wp-includes, or bootstrap internals. Proper routing prevents misrouting tasks to Gutenberg and ensures correct component ownership.

Related Skills

Explore More Software Engineering Skills→
wpacademywpacademy
65

wp-plugin-review

Analyze WordPress plugins with PHPCS, PHPStan, and PHPUnit and generate a Markdown report.

Community
Advanced
sjinkssjinks

wp-plugin-version-diff

Generate unified diff patches between WordPress plugin versions.

Community
Advanced
WesleySmitsWesleySmits
6

generating-wordpress-fse-blocks

Generate WordPress Full Site Editing blocks and theme scaffolding.

Community
Advanced
ArabelaTsoArabelaTso
142

bug-to-patch-generator

Generate code patches from bug reports and failing tests.

Community
Advanced