php-cleanup

Detect and remove unused PHP code and dependencies in WordPress projects.

1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/iwritec0de/wp-dev --skill php-cleanup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: php-cleanup
Source: https://github.com/iwritec0de/wp-dev/tree/main/skills/php-cleanup
Command: npx skills add https://github.com/iwritec0de/wp-dev --skill php-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and cleans unused PHP code, dead code, and missing dependencies in WordPress projects, helping teams reduce bloat and prevent runtime errors.

Core Features & Use Cases

  • Detect unused PHP code and dead code using Psalm, composer-unused, and PHP-CS-Fixer
  • Identify missing composer dependencies with composer-require-checker
  • Clean up unused imports and stale dependencies in WordPress plugins/themes
  • Real-world use case: prune legacy code to shrink autoload size and boost performance

Quick Start

Run the cleanup workflow on your WordPress PHP project to identify dead code and remove unused dependencies

Frequently Asked Questions about php-cleanup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find and remove unused PHP code in WordPress plugins?

Detect unused PHP code in WordPress plugins by analyzing source files and composer.json with Psalm and PHP-CS-Fixer. This identifies dead code, unused imports, and orphaned dependencies to shrink autoload size and reduce bloat.

What is the best way to detect missing composer dependencies in WordPress themes?

Detecting missing composer dependencies in WordPress themes requires analyzing composer.json against actual PHP usage patterns using composer-require-checker. This prevents runtime errors by identifying packages referenced in code but missing from project dependencies.

Can I use composer-unused to clean up stale dependencies in PHP projects?

Yes, composer-unused identifies stale dependencies listed in composer.json but never referenced in the PHP source code. Removing these orphaned packages reduces project bloat and keeps the autoloader optimized for performance.

Does static analysis with Psalm help identify dead code in legacy WordPress projects?

Static analysis with Psalm identifies dead code in legacy WordPress projects by tracing execution paths and flagging unreachable code blocks. Combined with composer-require-checker, it guides safe cleanup of unused imports and missing dependencies without breaking runtime behavior.

Why does my WordPress plugin have bloated autoload files after cleanup?

Bloated autoload files in WordPress plugins occur when unused classes and stale dependencies remain in composer.json. Running composer-unused and PHP-CS-Fixer detects and prunes orphaned dependencies and dead code, shrinking the autoload footprint and boosting performance.