review-pr

To automate PR review and generate a markdown report, this Skill identifies changes between your current branch and its merge-base. It outputs a severity-tagged report containing file paths, line numbers, and a final risk assessment.

Analyzing git branch diffs against a clean upstream merge-base involves resolving the correct target based on upstream refs. This process fetches the latest refs, inspects changed files, and surfaces risk signals to ensure accurate code quality checks.

Yes, this automated branch review tool works with git worktrees. It applies the review workflow across managed worktrees and multiple projects, streamlining code quality checks by computing the merge-base and selecting the correct target branch.

Severity findings and risk assessments in the generated review report are structured by severity level. The final markdown report includes specific file paths, line numbers, and a final risk assessment, stored under reviews/<project>/ with a date-stamped filename.

Yes, you can use this PR diff analyzer without installing additional dependencies or components. The metadata indicates it requires no external dependencies or components to compute merge-bases and generate structured markdown review reports.

You should not use an automated markdown report generator for branch reviews if you require inline code annotations rather than standalone files. This tool outputs structured reports under a dated filename in reviews/<project>/ instead of modifying source files directly.