Skip to main content

php-code-review

Review PHP code using PhpStorm inspections. Use when editing PHP files, reviewing code quality, fixing PHP issues, or when asked about PHP best practices.

소스 정보

저장소
JetBrains/phpstorm-claude-marketplace
최근 소스 활동
2026년 7월 6일 15:07
감지된 SKILL.md 언어
영어
스타
34
포크
4

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
php-code-review
description
Review PHP code using PhpStorm inspections. Use when editing PHP files, reviewing code quality, fixing PHP issues, or when asked about PHP best practices.
# PHP Code Review Skill Use PhpStorm's inspection engine to ensure PHP code quality. This skill provides access to the same inspections shown in the IDE editor. ## When to Use - After editing PHP files (`.php`, `.phtml`) - When user asks to review PHP code quality - When fixing PHP-related issues - When asked about PHP best practices for this codebase ## Workflow ### 1. Run Inspections 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: - **severity**: ERROR > WARNING > WEAK_WARNING > INFORMATION - **line/column**: Exact location (1-based) - **description**: What's wrong - **quickFixes**: Available automated fixes (name + description) ### 2. Evaluate Results - **ERROR**: Must fix - code may not work correctly - **WARNING**: Should fix - potential bugs or bad practices - **WEAK_WARNING**: Consider fixing - style or minor issues - **INFORMATION**: Optional - suggestions for improvement ### 3. Apply Fixes 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. ### 4. Verify Re-run inspections to confirm issues are resolved.
GitHub에서 보기