Help us improve
Share bugs, ideas, or general feedback.
From phpstorm-plugin
Review PHP code using PhpStorm inspections. Use when editing PHP files, reviewing code quality, fixing PHP issues, or when asked about PHP best practices.
npx claudepluginhub jetbrains/phpstorm-claude-marketplace --plugin phpstorm-pluginHow this skill is triggered — by the user, by Claude, or both
Slash command
/phpstorm-plugin:php-code-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use PhpStorm's inspection engine to ensure PHP code quality. This skill provides access to the same inspections shown in the IDE editor.
Foundational PHP project knowledge for AI agents. Use when working on a PHP project, setting up a PHP development environment, understanding PHP project structure, following PHP coding standards, running PHP tests, using Composer, or when guidance on PHP-specific tools and workflows in PhpStorm is needed.
Analyzes PHP code for PSR-12 compliance and style issues including brace placement, line length, indentation, blank lines, trailing whitespace, use statements, array syntax, and operator spacing.
Automatically runs nette/coding-standard (ECS) on PHP files after every Edit/Write, fixing formatting and removing unused use statements. Essential for all PHP creation, editing, refactoring, or bug fixes to avoid import issues.
Share bugs, ideas, or general feedback.
Use PhpStorm's inspection engine to ensure PHP code quality. This skill provides access to the same inspections shown in the IDE editor.
.php, .phtml)Call get_inspections to analyze a PHP file:
get_inspections(
filePath: "path/to/file.php",
minSeverity: "WEAK_WARNING" # or ERROR, WARNING, INFORMATION
)
Returns problems with:
For issues with quick fixes, use apply_quick_fix:
apply_quick_fix(
filePath: "path/to/file.php",
line: 42,
column: 10,
quickFixName: "Safe delete '$unusedVar'"
)
Note: The quickFixName must match exactly what was returned by get_inspections. The tool re-runs highlighting at the specified location to find and apply the matching fix.
For issues without quick fixes, edit the file manually.
Re-run inspections to confirm issues are resolved.