pr-review-local

To run a local code review before pushing, you analyze your feature branch diff against its base branch to catch security vulnerabilities, regression risks, and performance anti-patterns without making external API calls. This generates a structured markdown report with line-referenced findings and severity labels.

A pre-push code review prevents regression risks by analyzing changed files locally for broken functionality and vulnerabilities before they reach the remote repository. It uses specialized subagents to scan the diff, catching issues early to avoid delayed feedback and messy PR review cycles.

Yes, you can perform a security audit on your git diff without creating a remote PR by running local-only analysis. This approach scans changed files for vulnerabilities and anti-patterns without GitHub API calls or comment posting, keeping your work private until you are ready to share.

Local pre-push code review handles large diffs and lockfiles by automatically excluding lockfiles, generated assets, and minified code from analysis. If the diff is too large to review reliably, the process aborts to ensure accurate regression detection and gap detection for unreviewed files.

The best way to detect performance anti-patterns in a feature branch before pushing is using parallel specialized subagents that analyze your diff for N+1 query patterns and similar issues. This local execution identifies problems early, producing a structured markdown report with severity labels.

A pre-push review aborts on very large feature branch diffs to prevent unreliable analysis and ensure accurate regression detection. By filtering out lockfiles and generated assets, the review focuses on meaningful code changes, providing gap detection for unreviewed files instead of failing silently.