mirror of
https://github.com/tiennm99/ccs.git
synced 2026-09-02 20:24:21 +00:00
style(ci): enhance ai-review prompt with rich emoji formatting
- 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:
@@ -101,25 +101,26 @@ jobs:
|
|||||||
|
|
||||||
## Review Focus Areas
|
## Review Focus Areas
|
||||||
|
|
||||||
1. **Security** - OWASP Top 10, injection, auth bypass, secrets exposure
|
1. 🔒 **Security** - OWASP Top 10, injection, auth bypass, secrets exposure
|
||||||
2. **Correctness** - Logic errors, edge cases, error handling
|
2. ✅ **Correctness** - Logic errors, edge cases, error handling
|
||||||
3. **Architecture** - Coupling, cohesion, API contracts, backward compatibility
|
3. 🏗️ **Architecture** - Coupling, cohesion, API contracts, backward compatibility
|
||||||
4. **Testing** - Coverage, edge cases, test quality
|
4. 🧪 **Testing** - Coverage, edge cases, test quality
|
||||||
5. **Performance** - Algorithm complexity, memory leaks, query efficiency
|
5. ⚡ **Performance** - Algorithm complexity, memory leaks, query efficiency
|
||||||
6. **Maintainability** - Naming, complexity, consistency with codebase
|
6. 📖 **Maintainability** - Naming, complexity, consistency with codebase
|
||||||
|
|
||||||
## Output Structure
|
## Output Structure
|
||||||
|
|
||||||
Use visual hierarchy with `---` separators between major sections:
|
Use visual hierarchy with emojis and `---` separators between major sections:
|
||||||
- Summary (2-3 sentences)
|
- 📋 **Summary** (2-3 sentences)
|
||||||
- Strengths (numbered, with file:line references)
|
- ✅ **Strengths** (numbered, with file:line references, use ⭐ for exceptional items)
|
||||||
- Observations & Suggestions (with code examples)
|
- 🔍 **Observations & Suggestions** (with code examples, priority tags)
|
||||||
- Security Considerations (✅/❌ checklist)
|
- 🔒 **Security Considerations** (✅/❌ checklist table)
|
||||||
- Code Quality Checklist (✅/❌ format)
|
- 📊 **Code Quality Checklist** (✅/❌ table format)
|
||||||
- Recommendations (Priority: High/Medium/Low)
|
- 💡 **Recommendations** (🔴 High / 🟡 Medium / 🟢 Low priority)
|
||||||
- Overall Assessment (APPROVED/APPROVED WITH NOTES/CHANGES REQUESTED)
|
- 🎯 **Overall Assessment** (✅ APPROVED / ⚠️ APPROVED WITH NOTES / ❌ CHANGES REQUESTED)
|
||||||
|
|
||||||
Be thorough but concise. Skip empty sections. Include code examples for non-trivial suggestions.
|
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:
|
End your review with:
|
||||||
> 🤖 Reviewed by `${{ env.REVIEW_MODEL }}`
|
> 🤖 Reviewed by `${{ env.REVIEW_MODEL }}`
|
||||||
|
|||||||
Reference in New Issue
Block a user