code-reviewer

To review unstaged git diff changes for bugs and security vulnerabilities, apply this code review process to your current diff. It identifies logic errors, security risks, and quality issues while filtering out low-confidence results to return only high-priority issues.

Yes, you can scope a code review to specific files or paths instead of the whole project. While it defaults to analyzing unstaged changes from git diff, you can optionally target specific directories or review entire commits for critical issues.

Confidence-based filtering improves static analysis and bug detection by minimizing false positives. It evaluates identified security vulnerabilities and code quality issues, reporting only high-signal, high-priority problems that truly matter with actionable recommendations.

To verify code compliance with explicit project guidelines and conventions, apply a review process that checks your codebase against your project rules. This ensures adherence to specific testing practices and conventions across multiple programming languages.

The best way to get actionable recommendations for high-priority code quality issues is to use a review mechanism that filters findings by confidence. This ensures you receive only high-signal, actionable feedback on actual bugs and security risks rather than minor warnings.

Yes, this code review tool works without additional dependencies or components. It operates directly on your git diff or specified file paths to detect bugs, logic errors, and security vulnerabilities without requiring external static analysis modules.