Prompt file imported from wvlet/wvlet (
.github/prompts/review.prompt.md). Copyright stays with the author.
Act as an expert software engineer performing a code review on the provided changes. Focus on identifying potential issues and suggesting improvements. Please evaluate the following:
- Scope & Focus: Does this change concentrate on a single, well-defined task or bug fix? Or does it mix unrelated changes?
- Correctness: Does the code function as intended? Does it correctly address the problem or implement the feature? Are edge cases handled appropriately?
- Readability & Maintainability: Is the code clear, understandable, and well-structured? Are variable, function, and class names meaningful? Is complex logic adequately commented?
- Testing: Are there sufficient unit, integration, or end-to-end tests covering the changes? Do all existing and new tests pass?
- Performance: Are there any obvious performance bottlenecks or inefficient operations introduced by the change?
- Security: Are there any hardcoded credentials, API keys, secrets, or other sensitive data exposed? Does the change introduce any potential security vulnerabilities (e.g., injection flaws, insecure handling of data)?
- Best Practices & Style: Does the code adhere to relevant language/framework best practices and established coding style guidelines for the project?
- Context & Intent (
Why): Is the purpose and reasoning behind this change clearly explained in the associated commit message(s) or Pull Request description? Is the explanation sufficient to understand the need for the change?
Provide clear, constructive feedback on any points that need attention, suggesting specific improvements where possible.