diagnostic-code-quality

WordPress Code Quality Diagnostic Skill

This skill performs comprehensive code quality analysis on custom WordPress code using a tiered approach to maximize efficiency while providing deep, actionable insights.

Analysis Scope

Analyze: Active theme + custom (non-WP.org) plugins only Skip: Core WordPress files and plugins from the WordPress.org repository (version audit handles those)

Section 1: Target Selection

Before analysis, determine which code to scan based on the connected WordPress site.

Step 1.1: Identify Active Theme

Get the active theme (parent) and child theme if applicable:

# Get active parent theme
ssh {user}@{host} "cd {wp_path} && {wp_cli_path} option get template"

# Get active stylesheet (child theme if different from template)
ssh {user}@{host} "cd {wp_path} && {wp_cli_path} option get stylesheet"

Scan targets: All PHP and JS files in:

• .sites/{site-name}/wp-content/themes/{template}/ (parent theme)
• .sites/{site-name}/wp-content/themes/{stylesheet}/ (child theme if different)

Step 1.2: Identify Custom Plugins

For each plugin directory in .sites/{site-name}/wp-content/plugins/, determine if it's a custom plugin or from WordPress.org:

WP.org Plugin Detection Heuristic:

1. Check if readme.txt exists with "Stable tag:" header
2. Verify the slug exists on WordPress.org API:

   curl -s "https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request[slug]={dirname}" | grep -q '"error"'
   

3. If API returns error (not found on WP.org) = CUSTOM PLUGIN → Do full code analysis
4. If API returns plugin info = WP.org plugin → SKIP code analysis (version audit handles this)

Alternative: Check plugin headers for "Plugin URI" pointing to wordpress.org domains

Step 1.3: List Scan Targets

Before proceeding, output a list of all selected targets:

Code Quality Scan Targets:
- Theme: {theme-name} ({file-count} files)
- Child Theme: {child-theme-name} ({file-count} files) [if applicable]
- Custom Plugins:
  - {plugin-1-name} ({file-count} files)
  - {plugin-2-name} ({file-count} files)

Total scan targets: {N} files across {M} directories