woocommerce-code-review_skill

This skill reviews WooCommerce code changes for coding standards, ensuring PHP backend, UI copy, and testing align with project conventions.
  • PHP

10.2k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill woocommerce/woocommerce --skill woocommerce-code-review

  • SKILL.md3.4 KB

Overview

This skill reviews WooCommerce code changes for compliance with WooCommerce coding standards and conventions. I scan PHP backend code, tests, and UI copy to find critical violations, group related issues, and provide actionable fixes. The output follows a concise, machine- and human-readable format that points to the relevant standard and a minimal corrective example.

How this skill works

I analyze diffs or local changes and look specifically for critical violations in architecture, naming, documentation, data integrity, testing, and UI text. For each issue I report the type, exact location, the applicable standard, and a short fix or code example. I group related findings and explain why the standard exists when that helps the reviewer or author.

When to use it

  • Performing automated PR reviews for WooCommerce repositories.
  • Reviewing local changes before opening a pull request.
  • Auditing code quality across backend PHP, tests, and UI copy.
  • Enforcing team conventions during code reviews.
  • Training new contributors on WooCommerce standards.

Best practices

  • Prioritize critical violations first (architecture, data integrity, major naming/convention errors).
  • Cite the exact standard file when flagging an issue so the author can learn the rule.
  • Provide minimal, correct examples rather than long rewrites.
  • Group related issues (naming, docblocks, tests) to reduce review noise.
  • Be constructive: explain why the rule exists and downstream risks of ignoring it.

Example use cases

  • Flagging standalone functions that should be class methods and pointing to file-entities guidance.
  • Detecting direct use of new for DI-managed classes and suggesting $container->get().
  • Finding camelCase method names and providing the snake_case replacement.
  • Reporting missing @since or missing/verbose docblocks with a one-line docblock example.
  • Checking test conventions like $sut naming, @testdox presence, and test file placement.
  • Catching sentence-case violations in UI text and suggesting the corrected label.

FAQ

Each violation includes an issue type, file path and line, the referenced standard, and a concise fix example.

Do you auto-fix issues?

I provide exact fix suggestions and examples but do not mutate code; use the suggestions to apply changes or create automated linters/patches.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational