git-diff-ai-reviewer 1.2.4 → 1.2.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/src/prompts.js +8 -3
- package/src/provider.js +1 -1
package/package.json
CHANGED
package/src/prompts.js
CHANGED
|
@@ -56,10 +56,14 @@ Your review MUST follow this exact output format for each finding:
|
|
|
56
56
|
---
|
|
57
57
|
|
|
58
58
|
Severity definitions:
|
|
59
|
-
- CRITICAL: Bugs, security vulnerabilities, data loss risks, crashes, broken functionality. These MUST be fixed before merging.
|
|
60
|
-
- WARNING: Performance issues, bad practices, potential future bugs, missing error handling. Should be addressed.
|
|
59
|
+
- CRITICAL: Bugs, security vulnerabilities, data loss risks, crashes, broken functionality INTRODUCED by the diff. These MUST be fixed before merging.
|
|
60
|
+
- WARNING: Performance issues, bad practices, potential future bugs, missing error handling INTRODUCED by the diff. Should be addressed.
|
|
61
61
|
- SUGGESTION: Code style, readability improvements, refactoring opportunities, documentation. Nice to have.
|
|
62
62
|
|
|
63
|
+
IMPORTANT — Bug fixes vs. new bugs:
|
|
64
|
+
- If the diff FIXES a preexisting bug (the old/removed code was wrong and the new code corrects it), do NOT report it as CRITICAL or WARNING. Instead, acknowledge it positively in the SUMMARY or skip it entirely. A correct bug fix is not an issue — it is an improvement.
|
|
65
|
+
- Only use CRITICAL or WARNING for problems that the diff INTRODUCES or LEAVES UNFIXED (e.g., an incomplete fix that still has issues, a fix that introduces a new side effect, etc.).
|
|
66
|
+
|
|
63
67
|
Rules:
|
|
64
68
|
1. Be specific — reference exact file names and line numbers from the diff.
|
|
65
69
|
2. Provide concrete fix suggestions, not vague advice.
|
|
@@ -67,7 +71,8 @@ Rules:
|
|
|
67
71
|
4. Use the provided context to understand HOW the changed code is used and whether the changes are correct in that context.
|
|
68
72
|
5. Group related issues together if they share the same root cause.
|
|
69
73
|
6. At the end, provide a SUMMARY section with counts by severity level.
|
|
70
|
-
7. If the code looks good, say so — don't invent issues
|
|
74
|
+
7. If the code looks good, say so — don't invent issues.
|
|
75
|
+
8. If the diff is a correct bug fix, acknowledge it as a positive change rather than reporting it as a problem.${customRules}`;
|
|
71
76
|
}
|
|
72
77
|
|
|
73
78
|
/**
|