From 6dcc8b28601cba9067b248c9a6befb3f9c3e1d34 Mon Sep 17 00:00:00 2001
From: kaitranntt <kaitran.ntt@gmail.com>
Date: Thu, 8 Jan 2026 11:06:55 -0500
Subject: [PATCH] style(ci): enhance ai-review prompt with rich emoji
 formatting
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- Add emojis to review focus areas and output sections
- Use priority color indicators (🔴/🟡/🟢)
- Add ⭐ for exceptional strengths
- Request tables for checklists
- Improve visual scannability
---
 .github/workflows/ai-review.yml | 29 +++++++++++++++--------------
 1 file changed, 15 insertions(+), 14 deletions(-)

diff --git a/.github/workflows/ai-review.yml b/.github/workflows/ai-review.yml
index eaac91d5..50b0553f 100644
--- a/.github/workflows/ai-review.yml
+++ b/.github/workflows/ai-review.yml
@@ -101,25 +101,26 @@ jobs:
 
             ## Review Focus Areas
 
-            1. **Security** - OWASP Top 10, injection, auth bypass, secrets exposure
-            2. **Correctness** - Logic errors, edge cases, error handling
-            3. **Architecture** - Coupling, cohesion, API contracts, backward compatibility
-            4. **Testing** - Coverage, edge cases, test quality
-            5. **Performance** - Algorithm complexity, memory leaks, query efficiency
-            6. **Maintainability** - Naming, complexity, consistency with codebase
+            1. 🔒 **Security** - OWASP Top 10, injection, auth bypass, secrets exposure
+            2. ✅ **Correctness** - Logic errors, edge cases, error handling
+            3. 🏗️ **Architecture** - Coupling, cohesion, API contracts, backward compatibility
+            4. 🧪 **Testing** - Coverage, edge cases, test quality
+            5. ⚡ **Performance** - Algorithm complexity, memory leaks, query efficiency
+            6. 📖 **Maintainability** - Naming, complexity, consistency with codebase
 
             ## Output Structure
 
-            Use visual hierarchy with `---` separators between major sections:
-            - Summary (2-3 sentences)
-            - Strengths (numbered, with file:line references)
-            - Observations & Suggestions (with code examples)
-            - Security Considerations (✅/❌ checklist)
-            - Code Quality Checklist (✅/❌ format)
-            - Recommendations (Priority: High/Medium/Low)
-            - Overall Assessment (APPROVED/APPROVED WITH NOTES/CHANGES REQUESTED)
+            Use visual hierarchy with emojis and `---` separators between major sections:
+            - 📋 **Summary** (2-3 sentences)
+            - ✅ **Strengths** (numbered, with file:line references, use ⭐ for exceptional items)
+            - 🔍 **Observations & Suggestions** (with code examples, priority tags)
+            - 🔒 **Security Considerations** (✅/❌ checklist table)
+            - 📊 **Code Quality Checklist** (✅/❌ table format)
+            - 💡 **Recommendations** (🔴 High / 🟡 Medium / 🟢 Low priority)
+            - 🎯 **Overall Assessment** (✅ APPROVED / ⚠️ APPROVED WITH NOTES / ❌ CHANGES REQUESTED)
 
             Be thorough but concise. Skip empty sections. Include code examples for non-trivial suggestions.
+            Use tables for checklists. Bold important terms. Make the review visually scannable.
 
             End your review with:
             > 🤖 Reviewed by `${{ env.REVIEW_MODEL }}`