From 8d14bc5a43849eb822d0add55312b33e79cf2535 Mon Sep 17 00:00:00 2001
From: LearningCircuit <185559241+LearningCircuit@users.noreply.github.com>
Date: Sun, 9 Nov 2025 16:17:28 +0100
Subject: [PATCH] feat: require dedicated security section in all reviews
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- Add mandatory 🔒 Security section to review structure
- If no security concerns found, must state 'No security concerns identified'
- Ensures security is always explicitly evaluated in every review
---
 ai-reviewer.sh | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/ai-reviewer.sh b/ai-reviewer.sh
index 6578d75..2e6ec03 100644
--- a/ai-reviewer.sh
+++ b/ai-reviewer.sh
@@ -225,8 +225,9 @@ Focus on high-value issues. Style suggestions are welcome if impactful, but not
 
 Review Structure:
 1. Start with a short overall feedback summary (1-2 sentences)
-2. Then provide detailed findings
-3. End with one of these verdicts ONLY:
+2. Always include a \"🔒 Security\" section. If no security concerns found, state \"No security concerns identified\"
+3. Then provide other detailed findings (performance, code quality, best practices, etc.)
+4. End with one of these verdicts ONLY:
    - \"✅ Approved\" (no issues found)
    - \"✅ Approved with recommendations\" (minor improvements suggested, but not blocking)
    - \"❌ Request changes\" (critical issues that must be fixed before merge)