tiennm99/ccs
1
0
Fork 0
mirror of https://github.com/tiennm99/ccs.git synced 2026-07-16 20:17:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

style(ci): enhance ai-review prompt with rich emoji formatting

Browse Source 
- Add emojis to review focus areas and output sections
- Use priority color indicators (🔴/🟡/🟢)
- Add ⭐ for exceptional strengths
- Request tables for checklists
- Improve visual scannability
This commit is contained in:
kaitranntt
2026-01-08 11:06:55 -05:00
parent 55049120ae
commit 6dcc8b2860
1 changed files with 15 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/ai-review.yml
+15 -14
View File
@@ -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 }}`