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.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, token-efficient review checklist with clear workflow and one-level-deep references to sibling skills. Its main gap is actionability: most violation categories rely on external skill files for concrete code examples rather than embedding them.

Suggestions

Add a brief inline Wrong/Right code pair for the highest-frequency backend violations (e.g. camelCase vs snake_case, `new` vs `$container->get()`) so the skill is actionable without requiring the sibling skill to be loaded.

Expand the single UI-copy example pattern to one backend example, since the PHP violations are the bulk of the checklist yet have no inline illustration.

Tighten the 'Notes' section, which partially repeats the referencing guidance already conveyed by the inline links.

Dimension	Reasoning	Score
Conciseness	The body is lean: grouped one-line violation entries with links, a short review approach, and a compact output template, with no padding or explanations of concepts Claude already knows; every section earns its place.	3 / 3
Actionability	Most violation entries are abstract one-liners ('Must use class methods', 'Must use snake_case') that delegate concrete wrong/right examples to linked sibling-skill files, and only the UI copy section shows explicit Wrong/Correct pairs; guidance is actionable as a checklist but incomplete on concrete examples, matching level 2.	2 / 3
Workflow Clarity	The 'Review Approach' gives a clear 5-step numbered sequence (scan, cite, provide examples, group, be constructive) and the 'Output Format' template structures results; this is a non-destructive single-pass review so the destructive-operation validation cap does not apply.	3 / 3
Progressive Disclosure	No bundle files exist under references/scripts/assets, so scoring is on structure: the body is a concise overview with clearly signaled one-level-deep markdown links to sibling skills (e.g. [file-entities.md](../woocommerce-backend-dev/file-entities.md)), well organized into sections with easy navigation.	3 / 3
	Total	11 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description with an explicit 'Use when' trigger and good natural keyword coverage. Its only weakness is that the capability statement is a single action rather than a list of concrete actions.

Dimension	Reasoning	Score
Specificity	The phrase 'Review WooCommerce code changes for coding standards compliance' names a concrete domain and action, but it describes a single review action rather than listing multiple specific concrete capabilities (e.g. flagging violations, citing standards, suggesting fixes), so it sits at level 2 rather than 3.	2 / 3
Completeness	It explicitly states what the skill does ('Review WooCommerce code changes for coding standards compliance') and when to use it ('Use when reviewing code locally, performing automated PR reviews, or checking code quality in WooCommerce projects'), satisfying both what and when with an explicit trigger clause.	3 / 3
Trigger Term Quality	'reviewing code locally, performing automated PR reviews, or checking code quality in WooCommerce projects' covers natural terms a user would say (code review, PR review, code quality, WooCommerce); it is not the level-2 'Works with PDF files' style of partial coverage.	3 / 3
Distinctiveness Conflict Risk	The WooCommerce coding-standards niche is specific and unlikely to trigger for unrelated skills; the trigger conditions are tied to WooCommerce projects specifically, giving it a clear niche with low conflict risk.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 13 suspicious	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Commit: c4889f6

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.