Merge pull request #4365 from woocommerce/dev/PCP-6288-cc-code-review-skill

CC Integration: New skill for code reviews

Author: stracker-phil

.claude/skills/code-review/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: code-review
+description: Reviews code changes for quality, security, and adherence to project standards. Use when reviewing PRs, commits, or staged changes.
+---
+
+# Code Review
+
+## Instructions
+
+When invoked, perform a thorough code review following these steps:
+
+### 1. Identify Changes to Review
+
+- If a PR number is provided as argument (e.g., `/code-review 123`), fetch the PR diff using `gh pr diff <number>`
+- If no argument provided, review staged changes with `git diff --cached`, or if nothing staged, review uncommitted changes with `git diff`
+- If a branch name is provided, compare against the main branch with `git diff develop...<branch>`
+
+### 2. Analyze PR
+
+- Read the PR description and comments for context
+- For each file with changes, evaluate:
+  - Code Quality: see [code-quality.md](code-quality.md)
+  - Check if there is any bug in the changes of the PR
+  - Testing Considerations
+
+### 3. Output Format
+
+Create a Markdown file report with the results and add it to ./temp/code-reviews including the PR id and title in the file name

.claude/skills/code-review/code-quality.md

@@ -0,0 +1,58 @@
+# Code Quality
+
+## Table of Contents
+
+- [Design Principles](#design-principles)
+- [Code Smells](#code-smells)
+- [Best Practices](#best-practices)
+
+## Design Principles
+
+### Single Responsible Principle
+
+Classes and methods should handle one single concept or responsibility.
+
+### Open Close Principle
+
+The Software should be open to extension and closed to modification.
+
+### Command Query Separation principle
+
+A method should either return a value or perform a task but not both.
+
+## Code Smells
+
+### Long classes and methods
+
+Long classes and methods that handles multiple concepts and responsibilities.
+
+### Primitive Obsession
+
+Instead of relying on primitive types (strings, arrays…) use dedicated objects that encapsulates the
+primitives and allows adding validation like Value Objects which allows:
+
+- Object integrity restrictions and validations that are not spread across the code base but in the
+  object itself.
+- Attracts related logic to the object
+- Adds semantics
+
+## Best Practices
+
+### Modularity
+
+Code inside `ExecutableModule::run` method should be added into WordPress hooks callbacks:
+
+Good:
+
+```php
+public function run( ContainerInterface $container ): bool {
+   add_action( 'admin_init', function () {
+      wp_enqueue_script( 'wc-store-ai' );
+```
+
+Bad:
+
+```php
+public function run( ContainerInterface $container ): bool {
+   wp_enqueue_script( 'wc-store-ai' );
+```