Launch and manage disposable WordPress playground environments via CLI.
npx skills add https://github.com/joseconti/mcp-skills --skill wp-playground-joseconti
Please help me install this Agent Skill. Skill: wp-playground Source: https://github.com/joseconti/mcp-skills/tree/main/wp-playground Command: npx skills add https://github.com/joseconti/mcp-skills --skill wp-playground-joseconti
WordPress development often requires isolated, disposable environments to test plugins, themes, and configurations without affecting production sites. WordPress Playground provides fast, reproducible instances either in-browser or via a CLI, enabling rapid experimentation and debugging.
Install the WP Playground CLI and start the server with automatic mounting to spin up a disposable WordPress environment.
High-intent search queries and answers about installing and using this skill.
You can spin up a disposable WordPress environment for testing by using the WordPress Playground CLI to launch isolated instances. This provides rapid, reproducible setups for safely testing plugins, themes, and configurations without affecting production sites.
A WordPress blueprint is a pre-defined configuration used to script WordPress setups, installs, and configurations. By running blueprint-driven setups, you can automate and reproduce exact environment states for consistent testing and debugging.
Yes, you can test WordPress plugins across different PHP and WP versions by switching versions on the fly within the WordPress Playground. This flexibility allows you to reproduce issues and verify compatibility across various environment configurations.
Yes, you need Node.js 20.18 or higher to run a local WordPress sandbox for debugging via the CLI. Once installed, you can mount a project path and optionally enable Xdebug for advanced issue reproduction.
To enable Xdebug in a WordPress playground to reproduce bugs, you use the environment's debug flexibility feature to turn on advanced debugging. This allows you to safely step through code in an isolated instance without impacting production sites.
The limitations of using an in-browser WordPress instance for testing include requiring Node.js 20.18+ and a mounted project path for CLI operations. It is designed for disposable, isolated testing rather than serving as a permanent production environment.
WPdoactionCreate disposable WordPress playgrounds for testing plugins and themes.
jnealey88Automate disposable WordPress environments for plugin and theme testing.
shogochiaiAutomates predefined tasks in repositoriesGitHub/GitLab, submitting pull requests for approval and seamlessly integrating with CI/CD pipelines to enforce code review and minimize manual effort. It handles everything from triggering builds to finalizing mergesGitLab/GitHub pull requests, ensuring your team's codebase stays healthy and your workflows stay on track, regardless of scale or complexity.
duthahookay, here's your tagline:)
