neuro-wp-plugin-debug

Audits WordPress plugin code for security vulnerabilities, standards violations, and performance issues.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/webdevarif/claude-skills --skill neuro-wp-plugin-debug-webdevarif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neuro-wp-plugin-debug
Source: https://github.com/webdevarif/claude-skills/tree/main/neuro-wp-plugin-debug
Command: npx skills add https://github.com/webdevarif/claude-skills --skill neuro-wp-plugin-debug-webdevarif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? WordPress plugin developers face rejection from WordPress.org, security breaches, and performance problems caused by missed bugs in their code. This Skill performs a systematic 10-stage audit covering coding standards, security, data handling, hooks, performance, REST API, and WordPress.org review requirements before submission. ## Core Features & Use Cases - Security Audit: Detects missing nonce verification, unescaped output, SQL injection, missing capability checks, insecure file uploads, and CSRF vulnerabilities with concrete wrong/right code examples. - WPCS Standards Enforcement: Checks WordPress Coding Standards compliance, prefixing rules for all globals, file naming conventions, and phpcs configuration. - Performance & Hook Debugging: Identifies N+1 queries, autoloaded option bloat, missing transient caching, hook priority conflicts, and remove_action failures with class instances. - Use Case: Before submitting a plugin to WordPress.org, run this audit to catch the sanitization, escaping, and readme.txt issues that cause 95% of review team rejections. ## Quick Start Review my WordPress plugin code for security vulnerabilities, coding standard violations, and WordPress.org rejection risks.

Frequently Asked Questions about neuro-wp-plugin-debug

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

FAQPage Schema
How do I check my WordPress plugin for security vulnerabilities?

Audit every form and AJAX handler for nonce verification, sanitize all superglobal input with functions like sanitize_text_field, escape all output with esc_html or esc_attr, and use $wpdb->prepare for every database query. Also verify capability checks with current_user_can on all administrative actions.

Why was my WordPress plugin rejected from WordPress.org?

Most rejections come from security issues: missing nonce checks, unescaped output, unprepared SQL queries, or generic unprefixed function and option names. Run Plugin Check (PCP) and a WPCS scan with the WordPress-Extra ruleset to catch these before resubmitting.

How do I run WordPress Coding Standards checks with phpcs?

Install WPCS via Composer with wp-coding-standards/wpcs, then run vendor/bin/phpcs with the WordPress-Extra standard. Configure a phpcs.xml.dist file defining your text domain, required prefixes, and minimum WordPress version for automated enforcement.

Why does remove_action not work on another plugin's class method?

remove_action requires the exact same object instance that was used in add_action, not a new instance or a string class name. You must obtain the original instance, typically through a singleton accessor, and pass the same priority.

What causes slow WordPress plugin performance?

Common causes include N+1 query patterns in loops, large options stored with autoload enabled, external HTTP requests without transient caching or timeouts, and missing database indexes. Enable SAVEQUERIES and Query Monitor to identify queries exceeding 50ms.