torbjorn/my-pal-mcp-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

enhance: improve code review prompt with technology-specific guidance

Browse Source 
Add comprehensive technology-specific review categories and instructions to analyze codebase technology stack before reviewing. This enhancement will provide more targeted and relevant code reviews by adapting to different frameworks and patterns.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Fahad
2025-06-10 13:52:24 +04:00
parent 157f80b47b
commit 7a5c9bfb8d
1 changed files with 18 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
prompts/tool_prompts.py
View File

@@ -55,7 +55,11 @@ Your review approach:
5. Acknowledge good practices when you see them 5. Acknowledge good practices when you see them
6. Be constructive but thorough - don't sugarcoat serious issues that impact their objectives 6. Be constructive but thorough - don't sugarcoat serious issues that impact their objectives
Review categories: Review categories (adapt based on technology stack and code structure):
IMPORTANT: First analyze the codebase to understand the technology stack, frameworks, and patterns in use. Then identify which of these recommended categories apply and consider additional technology-specific concerns.
**Recommended base categories:**
- 🔴 CRITICAL: Security vulnerabilities (including but not limited to): - 🔴 CRITICAL: Security vulnerabilities (including but not limited to):
- Authentication/authorization flaws - Authentication/authorization flaws
- Input validation vulnerabilities - Input validation vulnerabilities
@@ -70,6 +74,19 @@ Review categories:
- 🟡 MEDIUM: Code smells, maintainability issues - 🟡 MEDIUM: Code smells, maintainability issues
- 🟢 LOW: Style issues, minor improvements - 🟢 LOW: Style issues, minor improvements
**Technology-specific considerations to evaluate:**
- **Web frameworks**: CSRF protection, input sanitization, session handling, middleware security
- **Database interactions**: Query optimization, connection pooling, migration safety, transaction handling
- **API design**: Rate limiting, authentication schemes, data validation, error handling
- **Frontend code**: Component lifecycle, state management, accessibility, performance
- **Microservices**: Service boundaries, communication patterns, fault tolerance, observability
- **DevOps/Infrastructure**: Configuration management, secrets handling, deployment safety
- **Testing**: Coverage gaps, test quality, mocking strategies, integration test patterns
- **Concurrency**: Thread safety, race conditions, deadlock prevention, async patterns
- **Third-party dependencies**: Version compatibility, security updates, license compliance
Always examine the code structure and imports to identify the specific technologies in use, then focus your review on the most relevant categories for that technology stack.
Format each issue as: Format each issue as:
[SEVERITY] File:Line - Issue description [SEVERITY] File:Line - Issue description
→ Fix: Specific solution with code example → Fix: Specific solution with code example