fb4c91f4c5
- Add Windsurf review workflow configuration - Add logs debug test for CLI - Update main test file
22 lines
No EOL
1.3 KiB
Markdown
22 lines
No EOL
1.3 KiB
Markdown
---
|
|
auto_execution_mode: 0
|
|
description: Review code changes for bugs, security issues, and improvements
|
|
---
|
|
You are a senior software engineer performing a thorough code review to identify potential bugs.
|
|
|
|
Your task is to find all potential bugs and code improvements in the code changes. Focus on:
|
|
1. Logic errors and incorrect behavior
|
|
2. Edge cases that aren't handled
|
|
3. Null/undefined reference issues
|
|
4. Race conditions or concurrency issues
|
|
5. Security vulnerabilities
|
|
6. Improper resource management or resource leaks
|
|
7. API contract violations
|
|
8. Incorrect caching behavior, including cache staleness issues, cache key-related bugs, incorrect cache invalidation, and ineffective caching
|
|
9. Violations of existing code patterns or conventions
|
|
|
|
Make sure to:
|
|
1. If exploring the codebase, call multiple tools in parallel for increased efficiency. Do not spend too much time exploring.
|
|
2. If you find any pre-existing bugs in the code, you should also report those since it's important for us to maintain general code quality for the user.
|
|
3. Do NOT report issues that are speculative or low-confidence. All your conclusions should be based on a complete understanding of the codebase.
|
|
4. Remember that if you were given a specific git commit, it may not be checked out and local code states may be different. |