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.
82
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/woocommerce-code-review/skills/woocommerce-code-review/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly communicates both what the skill does and when to use it, with good trigger terms for WooCommerce-specific code review scenarios. Its main weakness is that the capability description is somewhat general—it could benefit from listing specific actions like checking PHP coding standards, WordPress hooks, or WooCommerce-specific patterns to improve specificity and distinctiveness.
Suggestions
Add specific concrete actions like 'Checks PHP coding standards, validates WordPress hook usage, reviews WooCommerce-specific patterns and API usage'
Mention specific standards or tools (e.g., 'WPCS', 'PHP_CodeSniffer', 'WooCommerce PHPCS ruleset') to increase distinctiveness from generic code review skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (WooCommerce code) and a general action (review for coding standards compliance), but doesn't list specific concrete actions like checking naming conventions, validating hook usage, checking PHP standards, etc. | 2 / 3 |
Completeness | Clearly answers both what ('Review WooCommerce code changes for coding standards compliance') and when ('Use when reviewing code locally, performing automated PR reviews, or checking code quality in WooCommerce projects') with explicit trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'WooCommerce', 'coding standards', 'PR reviews', 'code quality', 'code changes', 'reviewing code'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The WooCommerce specificity helps distinguish it, but 'code quality' and 'PR reviews' are broad enough to potentially overlap with general code review or linting skills. Could be more distinct by mentioning specific WooCommerce/WordPress coding standards. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured code review checklist that effectively serves as a hub pointing to detailed standards in companion skills. Its main strength is the clear organization of violations by category with direct links to authoritative sources. The main weakness is that most violation entries lack concrete before/after code examples (the UI text section being the exception), which limits immediate actionability without consulting the referenced files.
Suggestions
Add concrete before/after PHP code examples for at least the most critical violations (e.g., show a standalone function vs. the correct class method approach, or `new ClassName()` vs. `$container->get()`)
Provide a complete, filled-in example of the output format template rather than just placeholders, so Claude can see exactly what a review comment should look like
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-organized. It doesn't explain what WooCommerce is or how code review works—it assumes Claude's competence and focuses on specific violations to flag with direct references to detailed standards. | 3 / 3 |
Actionability | The skill provides specific violation categories with wrong/correct examples for UI text, but most violations only reference external files rather than providing inline executable examples or concrete code snippets showing the fix. The output format template is helpful but uses placeholder text rather than a concrete example. | 2 / 3 |
Workflow Clarity | The 'Review Approach' section provides a clear 5-step sequence, but lacks validation checkpoints or feedback loops. For a code review workflow, there's no guidance on what to do when findings are ambiguous, how to prioritize violations, or how to verify fixes are correct. | 2 / 3 |
Progressive Disclosure | Excellent use of progressive disclosure—the skill serves as a concise overview/checklist with well-signaled, one-level-deep references to specific skill files (dependency-injection.md, code-entities.md, etc.) for detailed standards. Navigation is clear and organized by category. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- Reviewed
Table of Contents
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.