Woocommerce code review
Skill bg-szy/TOP-SKILLS/skills/marketplace/woocommerce-code-review
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能,提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill woocommerce-code-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Review WooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.
SKILL.md
3.8 KB, as published. Nobody here has run it
WooCommerce Code Review
Review code changes against WooCommerce coding standards and conventions.
Critical Violations to Flag
Backend PHP Code
Consult the woocommerce-backend-dev skill for detailed standards. Using these standards as guidance, flag these violations and other similar ones:
Architecture & Structure:
- ❌ Standalone functions - Must use class methods (file-entities.md)
- ❌ Using
newfor DI-managed classes - Classes insrc/must use$container->get()(dependency-injection.md) - ❌ Classes outside
src/Internal/- Default location unless explicitly public (file-entities.md)
Naming & Conventions:
- ❌ camelCase naming - Must use snake_case for methods/variables/hooks (code-entities.md)
- ❌ Yoda condition violations - Must follow WordPress Coding Standards (coding-conventions.md)
Documentation:
- ❌ Missing
@sinceannotations - Required for public/protected methods and hooks (code-entities.md) - ❌ Missing docblocks - Required for all hooks and methods (code-entities.md)
- ❌ Verbose docblocks - Keep concise, one line is ideal (code-entities.md)
Data Integrity:
- ❌ Missing validation - Must verify state before deletion/modification (data-integrity.md)
Testing:
- ❌ Using
$instancein tests - Must use$sutvariable name (unit-tests.md) - ❌ Missing
@testdox- Required in test method docblocks (unit-tests.md) - ❌ Test file naming - Must follow convention for
includes/vssrc/(unit-tests.md)
Frontend JS/TS Code
Architecture & Structure:
- ❌ Barrel self-import (circular dependency) — a JS/TS file anywhere in the monorepo importing from its own package barrel (
from '../',from '../../',from '../index',from '../../index') when that barrel re-exports it. Relevant to SWC TDZ / esbuild tree-shaking / tsc incremental builds. Fix: use the direct module path instead.
UI Text & Copy
Consult the woocommerce-copy-guidelines skill. Flag:
- ❌ Title Case in UI - Must use sentence case (sentence-case.md)
- Wrong: "Save Changes", "Order Details", "Payment Options"
- Correct: "Save changes", "Order details", "Payment options"
- Exceptions: Proper nouns (WooPayments), acronyms (API), brand names
Review Approach
- Scan for critical violations listed above
- Cite specific skill files when flagging issues
- Provide correct examples from the skill documentation
- Group related issues for clarity
- Be constructive - explain why the standard exists when relevant
Output Format
For each violation found:
❌ [Issue Type]: [Specific problem]
Location: [File path and line number]
Standard: [Link to relevant skill file]
Fix: [Brief explanation or example]
Notes
- All detailed standards are in the
woocommerce-backend-dev,woocommerce-dev-cycle, andwoocommerce-copy-guidelinesskills - Consult those skills for complete context and examples
- When in doubt, refer to the specific skill documentation linked above