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.
65
77%
Does it follow best practices?
Impact
—
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 specific to WooCommerce development workflows. Its main weakness is that the capability description is somewhat general—'coding standards compliance' could be more specific about what standards or checks are performed. The distinctiveness could also be improved by emphasizing WooCommerce-specific aspects more strongly.
Suggestions
Add specific concrete actions like 'Checks PHP coding standards, validates hook naming conventions, reviews WooCommerce API usage patterns' to improve specificity.
Strengthen distinctiveness by mentioning WooCommerce-specific standards (e.g., 'WooCommerce/WordPress coding standards, PHPCS rules') to differentiate 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', 'code changes', 'coding standards', 'PR reviews', 'code quality', 'code review'. 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 conflict with generic PHP or WordPress code review skills. | 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 skill that effectively serves as a hub pointing to detailed standards in companion skills. Its main strength is concise organization with clear cross-references. Its weakness is that actionability relies heavily on external files, and the review workflow lacks explicit validation/verification steps for confirming flagged issues are genuine violations.
Suggestions
Add a concrete, fully filled-in example of a complete review output (not just the template) showing 2-3 actual violations with real file paths, line numbers, and fixes to improve actionability.
Add a verification step in the Review Approach (e.g., 'Before reporting, verify each flagged issue against the linked standard to avoid false positives') to strengthen workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. It avoids explaining what code review is or how WooCommerce works, and instead jumps straight into specific violations to flag. Every section earns its place with concrete, actionable items. | 3 / 3 |
Actionability | The skill provides specific violation categories with wrong/correct examples (e.g., sentence case), but most items are references to other skill files rather than inline executable guidance. The output format template is helpful but uses placeholder text rather than a concrete filled-in 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 skill involving potentially destructive feedback (flagging issues in PRs), there's no verification step to confirm findings are accurate or to handle ambiguous cases. | 2 / 3 |
Progressive Disclosure | The skill is an excellent overview that appropriately references detailed standards in sibling skill files with clear, one-level-deep links. Each violation category links to the specific relevant file, making navigation easy and keeping the main file concise. | 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
5e92b71
- 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.