メニュー
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".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | drupaltools-phpcs |
| description | 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 PHPCS in the project and resolve the violations it reports.
The PHPCS 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/phpcs
# Without DDEV
vendor/bin/phpcs
Run the command and capture the full output:
vendor/bin/phpcs
If PHPCS is not installed, install it first (use the same prefix from Step 1):
composer require --dev drupal/coder
PHPCS groups violations per file and lists each one with a line number, severity (ERROR/WARNING), and a fixable flag:
FILE: src/Controller/MyController.php
FOUND 2 ERRORS AFFECTING 2 LINES
15 | ERROR | [x] Line exceeds 80 characters
42 | ERROR | [ ] Missing function docblock
[x] means PHPCS can auto-fix it. [ ] means a manual fix is required.
Auto-fix everything fixable first with PHPCBF (same prefix rules):
vendor/bin/phpcbf
Then fix the remaining [ ] violations manually, one file at a time. Common ones:
| Issue | How to fix |
|---|---|
| Line exceeds 80 characters | Wrap or break the line |
| Missing file docblock | Add the standard Drupal file docblock |
| Missing function docblock | Add a real docblock or @inheritdoc |
| Format of docblock | Match the Drupal docblock style |
| Use of tabs | Replace with 2 spaces |
| Trailing whitespace | Remove it |
For each violation, open the file at the reported line, apply the fix, and move on. Read each file before editing.
Run PHPCS again. Repeat Step 4 until the run reports 0 errors. Stop when output says "No violations found" or shows a clean file list.
Finish with a short summary: files changed, errors fixed, warnings remaining.
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 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".
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".
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.