33 lines
1.5 KiB
Markdown
33 lines
1.5 KiB
Markdown
---
|
|
allowed-tools: Bash(glab mr:*), Bash(git branch:*), Bash(git log:*)
|
|
description: Review Merge Request
|
|
---
|
|
|
|
## Context
|
|
|
|
- Current MR status: !`glab mr view $ARGUMENTS --output json | jq -r '.state'`
|
|
- Current MR diff: !`glab mr diff $ARGUMENTS`
|
|
- Current branch: !`git branch --show-current`
|
|
- Recent commits: !`git log --oneline -10`
|
|
|
|
## Your task
|
|
|
|
You are an experienced code review expert. Please use `glab` to help me review the code changes submitted in the following Merge Request (MR) #$ARGUMENTS, and output the following structure:
|
|
|
|
1. **Change Summary**: Briefly describe the main changes in this MR.
|
|
2. **Potential Risks**: Point out possible issues that may be introduced, such as performance, maintainability, security, etc.
|
|
3. **Optimization Suggestions**: Provide reasonable improvement directions, skip if none.
|
|
4. **Compliance Check**: Whether it conforms to the current project's code style, naming conventions, module boundary division, etc.
|
|
|
|
Please output using chinese in structured Markdown format and use bullet lists as much as possible, then ask me if you need pushing the review comments.
|
|
|
|
# Optional Parameter Description
|
|
|
|
- `$LANGUAGE`: Code language (e.g., Python, PHP, TypeScript)
|
|
- `$SCOPE`: Review scope (e.g., focus only on performance, security, default is all)
|
|
|
|
Please adjust the focus based on parameters:
|
|
|
|
- When `$SCOPE=performance`, please pay special attention to loops, I/O, database calls, etc.
|
|
- When `$SCOPE=security`, please pay special attention to input validation, permission boundaries, SQL injection, etc.
|