Skip to content

Add wp-env skill for local WordPress development#38

Open
rushikeshmore wants to merge 1 commit intoWordPress:trunkfrom
rushikeshmore:add/wp-env-skill
Open

Add wp-env skill for local WordPress development#38
rushikeshmore wants to merge 1 commit intoWordPress:trunkfrom
rushikeshmore:add/wp-env-skill

Conversation

@rushikeshmore
Copy link
Copy Markdown

What?

Adds a new wp-env skill that teaches AI coding assistants how to set up, configure, and troubleshoot local WordPress development environments using @wordpress/env.

Addresses the community request in #9 (comment from @owlot: "Would love to see an wp-env skill").

Why?

@wordpress/env is the official Docker-based local development tool for WordPress plugin and theme development. It's referenced throughout the Gutenberg docs and used by core contributors, but there's no agent skill covering it. AI assistants currently guess at wp-env configuration and often make mistakes like using bare plugin slugs instead of ZIP URLs, or not checking Docker status before starting.

How?

New skill: skills/wp-env/SKILL.md

  • All 7 required sections (When to use, Inputs required, Procedure, Verification, Failure modes, Escalation)
  • Covers: installation, auto-detection (plugin/theme/core), .wp-env.json configuration, source string formats, WP-CLI commands, PHPUnit testing, Xdebug setup, multisite, override files, environment management
  • Common gotchas table (port conflicts, bare slugs, override merge behavior, Docker not running)

Eval scenarios: 2 JSON scenarios

  • wp-env-start-plugin.json -- setting up wp-env for a plugin project
  • wp-env-troubleshoot-port.json -- diagnosing and fixing port conflicts

README: Updated Available Skills table with wp-env entry.

Testing

  • node eval/harness/run.mjs passes
  • node shared/scripts/skillpack-build.mjs --clean builds successfully for all 4 targets (codex, vscode, claude, cursor)
  • Skill follows required SKILL.md structure with all 7 sections
  • Two eval scenarios added
  • Frontmatter validates (name matches folder, compatibility includes WP 6.9 + PHP 7.2.24+)

Use of AI Tools

Claude Code was used to assist with drafting this skill. Content was verified against the official @wordpress/env documentation and source code.

Add a new skill teaching AI assistants how to set up, configure, and
troubleshoot @wordpress/env local development environments.

Covers: installation, auto-detection, .wp-env.json configuration,
WP-CLI commands, PHPUnit testing, Xdebug, multisite, port conflicts,
and common failure modes.

Includes two eval scenarios:
- wp-env-start-plugin: setting up wp-env for plugin development
- wp-env-troubleshoot-port: diagnosing and fixing port conflicts

Addresses community request in WordPress#9.
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 9, 2026

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @rushikeshmore.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: rushikeshmore.


To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant