Add wp-env skill for local WordPress development#38
Open
rushikeshmore wants to merge 1 commit intoWordPress:trunkfrom
Open
Add wp-env skill for local WordPress development#38rushikeshmore wants to merge 1 commit intoWordPress:trunkfrom
rushikeshmore wants to merge 1 commit intoWordPress:trunkfrom
Conversation
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.
|
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 Unlinked AccountsThe 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. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Adds a new
wp-envskill 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/envis 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.wp-env.jsonconfiguration, source string formats, WP-CLI commands, PHPUnit testing, Xdebug setup, multisite, override files, environment managementEval scenarios: 2 JSON scenarios
wp-env-start-plugin.json-- setting up wp-env for a plugin projectwp-env-troubleshoot-port.json-- diagnosing and fixing port conflictsREADME: Updated Available Skills table with wp-env entry.
Testing
node eval/harness/run.mjspassesnode shared/scripts/skillpack-build.mjs --cleanbuilds successfully for all 4 targets (codex, vscode, claude, cursor)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.