Woocommerce code review

Skill VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/woocommerce-code-review/skills/woocommerce-code-review

Review WooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality in WooCommerce projects.From its SKILL.md

Install

npx -y skills add VRIL-LABS/skill-jam --skill woocommerce-code-review

Assembled 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.
0 stars0 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.

SKILL.md

3.4 KB, 714 tokens by cl100k_base, 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 new for DI-managed classes - Classes in src/ 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 @since annotations - 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 $instance in tests - Must use $sut variable name (unit-tests.md)
Missing @testdox - Required in test method docblocks (unit-tests.md)
Test file naming - Must follow convention for includes/ vs src/ (unit-tests.md)

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, and woocommerce-copy-guidelines skills
Consult those skills for complete context and examples
When in doubt, refer to the specific skill documentation linked above

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most code review skills give in 714 tokens

Counted across 668 of the 814 authors here whose files we hold, read 2026-09-06

Provide technical reasoning when pushing backin 84 of 668, across 70 files
Fix critical issues immediatelyin 77 of 668, across 60 files
Dispatch a code reviewer subagentin 76 of 668, across 59 files
Fix important issues before proceedingin 73 of 668, across 56 files
Ask for clarification on unclear itemsin 68 of 668, across 56 files
Verify feedback against codebase before implementationin 66 of 668, across 55 files
Implement fixes one at a timein 64 of 668, across 53 files
Test each fix individuallyin 62 of 668, across 51 files
Restate technical requirements in own wordsin 57 of 668, across 46 files
Reply to inline comments in the specific threadin 51 of 668, across 40 files
Note minor issues for laterin 49 of 668, across 34 files
Group findings by severityin 48 of 668, across 47 files

Said here and by no other author read

Scan code for critical violations
Cite specific skill files for issues
Group related issues for clarity
Explain why standards exist
Use container get for dependency injection
Add since annotations to methods

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.