diff --git a/commands/web/wunderio-core-review.sh b/commands/web/wunderio-core-review.sh
new file mode 100644
index 0000000..b7b6de0
--- /dev/null
+++ b/commands/web/wunderio-core-review.sh
@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+
+#ddev-generated
+
+## Description: Runs AI code review commands.
+## Usage: review
+## Example: "ddev review"
+## ExecRaw: true
+
+wdr-core tooling review.sh "$@"
diff --git a/wunderio/core/tooling/review.sh b/wunderio/core/tooling/review.sh
new file mode 100755
index 0000000..3d0221d
--- /dev/null
+++ b/wunderio/core/tooling/review.sh
@@ -0,0 +1,210 @@
+#!/bin/bash
+#ddev-generated
+
+#
+# Helper script to perform AI Code Review on the current branch against a target branch (default: main).
+# Usage: ddev ai-review [target-branch]
+# Example: ddev ai-review
+# Example: ddev ai-review develop
+#
+
+set -eu
+if [[ -n "${WUNDERIO_DEBUG:-}" ]]; then
+    set -x
+fi
+
+# Try to source global helpers if they exist
+source "$WUNDERIO_GLOBAL_SCRIPT_ROOT/_helpers.sh" 2>/dev/null || true
+
+# Helper function for error messages if _helpers.sh isn't available
+display_error_message() {
+    echo -e "\033[31m$1\033[0m"
+}
+
+# Configuration from environment.
+OPENAI_API_URL="${OPENAI_API_URL:-}"
+OPENAI_API_KEY="${OPENAI_API_KEY:-}"
+# Modern models (Gemini 1.5/2.5 Pro, GPT-4o, Claude 3.5 Sonnet) are highly recommended for deep reviews.
+# Flash is fast, but Pro models catch more complex logic bugs.
+MODEL="google_genai.gemini-2.5-flash"
+
+# Validate environment variables.
+if [ -z "$OPENAI_API_URL" ] || [ -z "$OPENAI_API_KEY" ]; then
+    display_error_message "❌ Error: Required OpenAI environment variables are not set"
+    echo "Set the missing variables in DDEV global config, then restart your DDEV project:"
+    echo "  ddev config global --web-environment-add=\"OPENAI_API_URL=https://your-api-url\""
+    echo "  ddev config global --web-environment-add=\"OPENAI_API_KEY=your-api-key\""
+    echo "  ddev restart"
+    exit 1
+fi
+
+# Determine branches
+TARGET_BRANCH="${1:-main}"
+CURRENT_BRANCH=$(git branch --show-current 2>/dev/null || echo "HEAD")
+
+if [ "$CURRENT_BRANCH" = "$TARGET_BRANCH" ]; then
+    echo "ℹ️ You are currently on the '$TARGET_BRANCH' branch. Switch to a feature branch to perform a review."
+    exit 0
+fi
+
+# Verify the target branch exists
+if ! git show-ref --verify --quiet "refs/heads/$TARGET_BRANCH" && ! git show-ref --verify --quiet "refs/remotes/origin/$TARGET_BRANCH"; then
+    echo "⚠️  Target branch '$TARGET_BRANCH' does not exist locally."
+    # Auto-fallback to master if user left the default as main
+    if [ "$TARGET_BRANCH" = "main" ] && (git show-ref --verify --quiet "refs/heads/master" || git show-ref --verify --quiet "refs/remotes/origin/master"); then
+        echo "🔄 Falling back to 'master'..."
+        TARGET_BRANCH="master"
+    else
+        display_error_message "❌ Error: Cannot compare against '$TARGET_BRANCH' because it does not exist."
+        exit 1
+    fi
+fi
+
+echo "🕵️  Analyzing changes on '$CURRENT_BRANCH' against '$TARGET_BRANCH' using ${MODEL}..."
+
+# Gather git context.
+# We use TRIPLE DOT (...) to show only changes on the current branch since it diverged from the target.
+# We use -U8 to give the AI 8 lines of surrounding code context (crucial for spotting bugs).
+# We exclude lock files, compiled assets, and large auto-generated files.
+DIFF=$(git diff "${TARGET_BRANCH}...HEAD" -M -w -U8 \
+    ':(exclude)*package-lock.json' \
+    ':(exclude)*yarn.lock' \
+    ':(exclude)*pnpm-lock.yaml' \
+    ':(exclude)*composer.lock' \
+    ':(exclude)*.min.js' \
+    ':(exclude)*.min.css' \
+    ':(exclude)*.svg')
+
+if [ -z "$DIFF" ]; then
+    echo "✅ No meaningful differences found between '$CURRENT_BRANCH' and '$TARGET_BRANCH' (excluding lockfiles/assets)."
+    exit 0
+fi
+
+# Truncate diff if it's too large to avoid exceeding API token limits.
+# 100,000 chars is usually safe for modern models like Gemini 2.5 and GPT-4o.
+MAX_DIFF_SIZE=100000
+DIFF_LENGTH=${#DIFF}
+if [ "$DIFF_LENGTH" -gt "$MAX_DIFF_SIZE" ]; then
+    echo "⚠️  Warning: Diff is very large (${DIFF_LENGTH} chars). Truncating to first ${MAX_DIFF_SIZE} characters for API request."
+    DIFF="${DIFF:0:$MAX_DIFF_SIZE}"
+    DIFF="${DIFF}"$'\n'$'\n'"[... diff truncated due to size ...]"
+fi
+
+# Build context
+CONTEXT="Comparing branch: ${CURRENT_BRANCH} against ${TARGET_BRANCH}
+
+--- BRANCH CHANGES ---
+${DIFF}"
+
+# Strict Senior Engineer Prompt (The secret to Copilot-quality reviews)
+REVIEW_INSTRUCTIONS="You are an expert Senior Software Engineer performing a pull-request code review.
+Your goal is to ensure code quality, security, and performance.
+
+CRITICAL RULES:
+1. FOCUS ON HIGH-VALUE ISSUES: Look for logical bugs, security vulnerabilities (XSS, SQLi, insecure data), race conditions, and unhandled edge cases.
+2. IGNORE NITPICKS: Do not comment on formatting, styling, or minor naming conventions (assume automated linters handle this).
+3. BE SPECIFIC: If you find an issue, mention the specific file and line/function.
+4. PROVIDE SOLUTIONS: When pointing out a bug, provide a brief, concrete code suggestion to fix it.
+5. IF NO ISSUES: If the code looks robust and safe, simply reply with: '✅ The branch looks good. No major issues found.'
+
+Format your response in Markdown:
+- Use '### [File Name]' as headers.
+- Use '- **[Issue Type]**: [Description]' for points.
+- Provide \`\`\` language specific code blocks \`\`\` for suggestions."
+
+JQ_ERROR_FILE=$(mktemp)
+# Ensure the file is deleted even if the script crashes or is killed.
+trap 'rm -f "$JQ_ERROR_FILE"' EXIT
+
+# Build JSON payload with jq (handles escaping properly)
+PAYLOAD=$(
+  model="$MODEL" \
+  context="$CONTEXT" \
+  instructions="$REVIEW_INSTRUCTIONS" \
+  jq -n \
+  '{
+    model: $ENV.model,
+    messages:[
+      {
+        role: "system",
+        content: $ENV.instructions
+      },
+      {
+        role: "user",
+        content: ("Please review the following pull-request style changes:\n\n" + $ENV.context)
+      }
+    ],
+    temperature: 0.2,
+    max_tokens: 4000
+  }' 2>"$JQ_ERROR_FILE"
+)
+JQ_EXIT_CODE=$?
+JQ_ERROR=$(cat "$JQ_ERROR_FILE" 2>/dev/null || echo "")
+
+# Validate that jq succeeded and produced valid JSON.
+if [ $JQ_EXIT_CODE -ne 0 ] || [ -z "$PAYLOAD" ] || [ "$PAYLOAD" = "null" ]; then
+    display_error_message "❌ Error: Failed to build API request payload"
+    if [ -n "$JQ_ERROR" ]; then echo "jq error: $JQ_ERROR"; fi
+    exit 1
+fi
+
+CURL_RESPONSE_FILE=$(mktemp)
+CURL_HTTP_CODE_FILE=$(mktemp)
+
+# Ensure temp files are cleaned up on exit.
+trap 'rm -f "$CURL_RESPONSE_FILE" "$CURL_HTTP_CODE_FILE" "$JQ_ERROR_FILE"' EXIT
+
+# Call API.
+set +e
+curl -s -f -X POST "${OPENAI_API_URL}/chat/completions" \
+  -H "Authorization: Bearer ${OPENAI_API_KEY}" \
+  -H "Content-Type: application/json" \
+  -d "$PAYLOAD" \
+  -w "%{http_code}" -o "$CURL_RESPONSE_FILE" > "$CURL_HTTP_CODE_FILE"
+CURL_EXIT_CODE=$?
+set -e
+
+HTTP_STATUS=$(cat "$CURL_HTTP_CODE_FILE" 2>/dev/null || echo "")
+RESPONSE=$(cat "$CURL_RESPONSE_FILE" 2>/dev/null || echo "")
+
+# Handle curl errors
+if [ $CURL_EXIT_CODE -ne 0 ] || [ "$HTTP_STATUS" -lt 200 ] ||[ "$HTTP_STATUS" -ge 300 ]; then
+    display_error_message "❌ Error: API request failed (cURL code: $CURL_EXIT_CODE, HTTP Status: $HTTP_STATUS)"
+    if [ -n "$RESPONSE" ]; then
+        echo "API Response (truncated): ${RESPONSE:0:300}..."
+    fi
+    exit 1
+fi
+
+# Extract message.
+JQ_REVIEW_MSG_ERROR_FILE=$(mktemp)
+trap 'rm -f "$JQ_REVIEW_MSG_ERROR_FILE" "$CURL_RESPONSE_FILE" "$CURL_HTTP_CODE_FILE" "$JQ_ERROR_FILE"' EXIT
+
+set +e
+REVIEW_MSG=$(echo "$RESPONSE" | jq -r '.choices[0].message.content' 2>"$JQ_REVIEW_MSG_ERROR_FILE")
+JQ_REVIEW_MSG_EXIT_CODE=$?
+set -e
+
+if [ $JQ_REVIEW_MSG_EXIT_CODE -ne 0 ] || [ -z "$REVIEW_MSG" ] || [ "$REVIEW_MSG" = "null" ]; then
+    display_error_message "❌ Error: Failed to parse API response"
+    exit 1
+fi
+
+# Print the final output
+echo ""
+echo "=========================================="
+echo "         🤖 AI CODE REVIEW REPORT         "
+echo "=========================================="
+echo ""
+
+# Try to use 'glow' for pretty Markdown rendering in the terminal if it's installed
+if command -v glow &> /dev/null; then
+    echo "$REVIEW_MSG" | glow -
+else
+    # Fallback to standard echo
+    echo -e "$REVIEW_MSG"
+fi
+
+echo ""
+echo "=========================================="
+echo ""