GitLab Merge Request Review

Perform code review on a GitLab merge rquest, add in-line comments and a summary.

Prerequisites

Required MCP Server: This prompt requires the gitlab-mr-mcp MCP server to be active and properly configured.

• Installation: Follow the setup instructions at https://github.com/upstash/context7
• Verification: Before running this prompt, ensure:
• The MCP server status light shows green
• All MCP functions are visible and properly loaded
  • If the server appears inactive, try toggling it Off/On and refresh
  • Wait for the status to show active before proceeding

Please help me review merge request #[MR_NUMBER] of the current project.

Make use of MCP tools from `gitlab-mr-mcp` MCP server:
- DO NOT use `get-projects`, instead getting project id from `general.mdc` 
- Use `get_merge_request_details` and `get_merge_request_diff` to fetch merge request details
- Use `add_merge_request_comment` and `add_merge_request_diff_comment` to add comments to the merge request

First, analyze the file types that have been changed in this merge request and load the appropriate Cursor rules based on file types.

Apply the appropriate rules when reviewing each file and ensure your feedback aligns with the project's established conventions as defined in these ruleset files.

Please follow these guidelines for the review:

1. Code Quality & Standards:
   - Follow language-specific best practices according to the Cursor rules
   - Ensure proper error handling and type safety where applicable
   - Check for code duplication and unnecessary complexity
   - Verify naming conventions and code formatting based on project standards
   - Look for potential memory leaks or performance issues
   - Ensure architecture principles are followed (e.g., hexagonal architecture for TypeScript)

2. Configuration & Environment:
   - Review environment variable changes
   - Check configuration file modifications
   - Verify deployment and infrastructure changes
   - Ensure secrets and sensitive data are handled properly

3. Documentation:
   - Verify README.md and documentation updates follow the standards in markdown.mdc
   - Check for clear and accurate documentation updates
   - Ensure configuration changes are properly documented
   - Look for missing documentation on new features

4. Testing & Reliability:
   - Look for missing test coverage
   - Check error handling scenarios
   - Verify edge cases are considered
   - Suggest additional test scenarios if needed

5. Performance & Scalability:
   - Review database queries and indexes
   - Check caching strategies and implementation
   - Look for N+1 query problems
   - Verify connection pooling and resource management

6. Security:
   - Check for security vulnerabilities
   - Verify proper input validation
   - Ensure secure handling of user data
   - Review authentication and authorization changes

For each file type, consider the following specific concerns:
- TypeScript/JavaScript: Type safety, functional patterns, component structure
- Python: PEP 8 compliance, error handling, docstrings
- Markdown: Documentation clarity, structure, completeness
- Configuration files: Environment variables, deployment settings
- CSS/SCSS: Style organization, responsiveness, accessibility
- Shell scripts: Error handling, permissions, portability

Please provide:
1. General comment that start with overall summary, followed by all the findings.
2. Detailed inline comments on specific code sections that expect code changes
3. DO NOT include a Final Summary comment

Add comments directly to the merge request where possible.

For each comment, please:
- Make it clear the comment it is made by Cursor IDE
- Include file names and line numbers
- The inline commment should be inserted right after the code referring to (line number + 1)
- Be specific and actionable
- Highlgiht any potential bugs or issues that need to be addressed
- Provide code examples for suggested improvements
- Explain the reasoning behind each suggestion
- Reference the specific Cursor rule that applies, if any