pr-review

Analyzing git diffs for merge readiness requires evaluating staged changes, working directory statuses, and commit history using git diff, git status, and git show outputs to assess code quality, security vulnerabilities, and potential conflicts before a safe merge.

Checking code quality across staged git changes is best done by applying a PR-style review to the diff output to detect lint and style adherence issues, security considerations, and potential defects. This structured analysis ensures the changes meet merge readiness criteria.

Yes, you can perform a PR review on uncommitted changes in your working directory by specifying the review scope as unstaged or staged. The analysis evaluates the git diff and git status outputs to provide a structured report of findings and recommended actions.

Assessing branch conflicts before a git merge is done by running a PR-style diff analysis across the target branches. This evaluates the git diff, status, and history outputs to detect potential conflicts, lint adherence, and security risks, providing a structured merge readiness report.

Yes, you need to provide git diff, git status, and git show outputs to perform a code review. The analysis requires these specific git command outputs to evaluate the diffs, statuses, and commit history accurately for quality, security, and merge readiness.