메뉴
Add or modify PooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.**
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | poocommerce-backend-dev |
| description | Add or modify PooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.** |
This skill provides guidance for developing PooCommerce backend PHP code according to project standards and conventions.
ALWAYS invoke this skill before:
*Test.php files)Follow PooCommerce project conventions when adding or modifying backend PHP code:
src/Internal/ by defaultAutomattic\PooCommerce namespaceTo determine the next PooCommerce version number for @since annotations:
$version property in includes/class-poocommerce.php on the trunk branch-dev suffix if present10.4.0-dev, use @since 10.4.0Review PooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.
Guidelines for UI text and copy in PooCommerce. Use when writing user-facing text, labels, buttons, or messages.
Run tests, linting, and quality checks for PooCommerce development. Use when running tests, fixing code style, or following the development workflow.
Setup and develop the PooCommerce block email editor. Use when working on email templates, transactional emails, or the email editor feature.
Commit uncommitted changes with well-crafted messages following PooCommerce repo conventions. Use when the user says "commit", "commit changes", "commit this", "git commit", or "save my work".
Create a high-quality draft PR for the current branch. Use when the user says "create a PR", "draft PR", "open a PR", "make a PR", "push and create PR", or "submit PR".