بنقرة واحدة
write-phpdocs
Write PHP DocBlocks with PHPStan support. DO NOT modify any code — only add/update documentation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Write PHP DocBlocks with PHPStan support. DO NOT modify any code — only add/update documentation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Convert hardcoded English strings in PHP files to WordPress i18n functions.
Perform a line-by-line security audit of a WordPress/WooCommerce plugin's source code and write findings to a ai-security-audit.md report with risk ratings. Use this skill whenever the user asks to audit, security-check, scan, or review plugin code for vulnerabilities, security issues, or weaknesses — especially when they mention the `includes` directory, a WooCommerce extension, SQLi/XSS/CSRF, nonce/capability/sanitization checks, or want a written security report. Trigger even if the user just says "check my plugin for security issues" without naming a specific vulnerability.
Fix Package JSON `devDependencies` and `dependencies` by sorting alphabetical order
| name | write phpdocs |
| description | Write PHP DocBlocks with PHPStan support. DO NOT modify any code — only add/update documentation. |
@package, @since, @version@name, description, @method — never use @extenddeclare( strict_types=1 ); after file level doc block.@param, @return, and @sincegit log -S "method_name" to find in which version it was introduced and add @since annotation with that version@since annotation with that version@see where methods relate to each other@template, @var) must support IDE autocompletion (PHPStorm etc.)handle_{hook_name}add_action() / add_filter() declarationsdo_action() / apply_filters()@param tags for each parameter passed to the hook/* translators: ... */ comments before translation strings (esc_html__, esc_html_e) wrapped in sprintf/printfgit log -S "hook_name" to find in which version it was introduced and add @since annotation with that versionGroup methods into logical sections with header comments:
// =====================================================================
// Service Lifecycle Methods
// =====================================================================
// =====================================================================
// Service Provider Registration Methods
// =====================================================================
// =====================================================================
// Setters
// =====================================================================
// =====================================================================
// ArrayAccess/Backwards Compatibility
// =====================================================================