Use when creating a new PHPStan stubs package for a WordPress plugin, theme, or Composer package — scaffolding the full repo structure (composer.json, configs/bootstrap.php, configs/finder.php, bin/generate.sh, bin/release-latest-versions.sh, .github/workflows/release.yml, phpstan.neon), fetching version lists from WP.org plugin API (api.wordpress.org/plugins) or Packagist API, using php-stubs/generator, or setting up the GitHub release workflow with jq. Triggers: \"create stubs for X plugin\", \"scaffold PHPStan stubs\", \"new stubs package\", \"add PHPStan stubs for WooCommerce\", \"stubs repo setup\", \"generate stub file\", \"PHPStan cannot find this class\", \"missing type hints for third-party plugin\", \"add stubs for this Composer package\", \"php-stubs/generator\", \"bin/generate.sh\", \"configs/bootstrap.php for stubs\", \"configs/finder.php\", \"release-latest-versions.sh\", \"WP.org plugin API for versions\", \"Packagist API for versions\", \"jq regex error in stubs script\", \"GitHub Actions release workflow for stubs\", \"phpstan.neon for stubs package\". Not for: configuring phpstan.neon in a plugin project or generating baselines — use the official wp-phpstan skill.
How to install wp-phpstan-stubs?
mralaminahamed/wp-dev-skills/wp-phpstan-stubs
$npx -y skills add mralaminahamed/wp-dev-skills --skill wp-phpstan-stubsInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/mralaminahamed/wp-dev-skills" --skill "mralaminahamed/wp-dev-skills/wp-phpstan-stubs"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/mralaminahamed/wp-dev-skills" that are relevant to the current task. Run `npx skills add "https://github.com/mralaminahamed/wp-dev-skills"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- tddTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.Jul 2026
- test-driven-developmentUse when implementing any feature or bugfix, before writing implementation codeJul 2026
- qaInteractive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues.Jul 2026
- verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output…Jul 2026
- webapp-testingToolkit for interacting with and testing local web applications using Playwright.Jul 2026
- playwright-best-practicesUse when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking…Jul 2026
