Menu
Run the custom PHPUnit test suite in a Drupal project and fix the reported failures and errors. Use this skill whenever the user asks to run phpunit, run the tests, run the custom testsuite, or says "run phpunit and fix the errors".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run the project markdownlint script in a Drupal project and fix the reported markdown violations. Use this skill whenever the user asks to run markdownlint, lint markdown, check the docs, or says "run scripts/markdownlint.sh and fix the errors".
Run PHPCS in a Drupal project and fix the reported coding standards violations. Use this skill whenever the user asks to run phpcs, check coding standards, fix code style errors, lint PHP/Drupal code, or says things like "run phpcs and fix the errors" or "clean up my coding standards".
Run PHPStan static analysis in a Drupal project and resolve the reported errors. Use this skill whenever the user asks to run phpstan, run static analysis, fix type errors, or says "run phpstan and fix the errors".
Estimate costs and timeline for Drupal projects using a structured breakdown of tasks, roles, content types, and development work. Use this skill when the user asks for a project quote, cost breakdown, timeline estimation, budget planning, or resource allocation for a Drupal website. Trigger for requests like "how much would this Drupal project cost", "estimate this project", "create a quote", "plan the budget", or any discussion about pricing/timeline for Drupal development.
Create a Drupal.org issue title and summary body that is ready to paste into the issue form. Use when the user asks to draft, improve, or rewrite an issue from a bug report, feature request, patch, MR, commit, or discussion. When the user says "issue title", "issue body", "issue summary", or similar.
Comprehensive guide for Drupal multilingual and translation workflows including interface translation, configuration translation, entity translation, PO/POT file management, and translation service integration. Use this skill when the user asks about Drupal translations, multilingual setup, i18n, translation modules, PO files, localization, or needs help with translation workflows, import/export, or external translation services.
| name | drupaltools-phpunit |
| description | Run the custom PHPUnit test suite in a Drupal project and fix the reported failures and errors. Use this skill whenever the user asks to run phpunit, run the tests, run the custom testsuite, or says "run phpunit and fix the errors". |
Run the custom test suite in the project and resolve the failures and errors it reports.
The PHPUnit command may need to run inside DDEV. Before running anything, make sure you are at the project root (the folder containing vendor/), then check whether the project uses DDEV:
[ -f .ddev/config.yaml ] && echo "uses_ddev" || echo "no_ddev"
uses_ddev, prefix every command in this skill with ddev exec.no_ddev, run every command directly with no prefix.# With DDEV
ddev exec vendor/bin/phpunit --testsuite custom
# Without DDEV
vendor/bin/phpunit --testsuite custom
Run the command and capture the full output:
vendor/bin/phpunit --testsuite custom
If PHPUnit is not installed, install it first (use the same prefix from Step 1):
composer require --dev phpunit/phpunit drupal/core-dev
PHPUnit separates problems into three kinds:
Failed asserting that X matches Y.For each problem note the test class, the test method, and the message with its stack trace.
For each failure or error, first decide whether the bug is in the code or in the test:
Read the test method and the code it exercises before editing. Common ones:
| Problem | How to fix |
|---|---|
| Failed asserting X matches Y | Fix the code so it produces the expected value, or correct the expectation |
| Class not found | Add a use statement or fix the namespace / autoloading |
| Call to undefined method | Correct the method name or add the method |
| Missing service / dependency | Declare the service and inject it, or add it to the test container |
| Exception thrown in test | Read the stack trace, fix the cause at the source |
| Database / kernel not bootstrapped | Extend KernelTestBase or BrowserTestBase as appropriate |
Re-run a single failing test while iterating to get feedback fast (same prefix rules):
vendor/bin/phpunit --testsuite custom --filter TestName
Run the full command again. Repeat Step 4 until all tests pass and the run reports OK or Tests: N, Assertions: M with no failures or errors.
Finish with a short summary: tests fixed, tests still failing, anything skipped.