agentleFS
Sign inStart free
JetBrainsKnown publisherJetBrains/phpstorm-claude-marketplace/skills/php-code-review/SKILL.md

php-code-review

Skill34 starsChanged 9 months agoMITView on GitHub

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

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. jeeinn/claude-skills★ 5same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use PhpStorm's inspection engine to ensure PHP code quality.

    line 8
  2. Very specific:

    After editing PHP files (.php, .phtml)

    line 12
  3. Distinctive:

    When user asks to review PHP code quality

    line 13
  4. Distinctive:

    When fixing PHP-related issues

    line 14
  5. Distinctive:

    When asked about PHP best practices for this codebase

    line 15
  6. Very specific:

    Call get_inspections to analyze a PHP file:

    line 21
  7. Distinctive:

    ERROR: Must fix - code may not work correctly

    line 38
  8. Distinctive:

    WARNING: Should fix - potential bugs or bad practices

    line 39
  9. Very specific:

    WEAK_WARNING: Consider fixing - style or minor issues

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free