code-quality-review

To review a git diff before pushing, analyze branch comparisons against master, staged work, or unstaged changes to surface actionable correctness, maintainability, and scope issues. Reading repository guidance, nearby implementation context, and changed tests ensures feedback matches local patterns.

Checking AI-generated code for missing edge cases requires a pre-merge advisory pass that reads touched paths and surrounding source. This risk-focused analysis identifies brittle logic, unnecessary abstractions, and missing verification coverage before you open a pull request.

Running a pre-push code review on staged or unstaged work involves examining the current diff against the correct base branch. The process surfaces only high-confidence findings related to regressions, structure drift, and touched security or performance concerns.

Yes, you can assess test coverage and security risks from a branch diff against master by reading changed tests and touched paths. This context-aware analysis evaluates verification coverage and highlights specific security or performance regressions introduced by the changes.

Use an advisory code review before pushing or opening a pull request to reduce avoidable rework and review churn. It is specifically suited for catching over-engineering and scope issues in AI-generated changes or branch comparisons prior to the standard merge process.