review

You can review uncommitted changes by gathering git diffs and applying static analysis across your working directory to surface bugs, security issues, and anti-patterns before committing.

Static analysis for code review is the process of examining source code without executing it to identify potential bugs, security concerns, and architectural problems. You need it to catch anti-patterns before they reach a commit.

Yes, automated code review can be applied across languages and repositories by assessing local working directory diffs and performing cross-file checks to provide structured feedback regardless of the specific tech stack.

The best way to find security vulnerabilities in a git diff is to enforce a multi-step workflow that gathers diffs, performs static analysis, and reviews context to output concrete findings with suggested remediations and risk assessments.

Static analysis catches cross-file dependency issues by enforcing cross-file checks within the review workflow, ensuring that uncommitted changes are evaluated for structural problems and anti-patterns across multiple modules.

You should not rely solely on automated code review when you lack uncommitted changes in your working directory, as the process strictly requires a git diff to gather context and generate actionable remediation feedback.