cmd-pr-review-prepare

To prepare a git branch for code review, you can run a pre-analysis skill that generates a context-rich diff against relevant branches and identifies potential issues before a human reviewer evaluates it. This streamlines the pull request process by building context automatically.

Automated pull request analysis examines git diffs to understand the scope of changes, flagging potential problems, cosmetic changes, and areas for code cleanup or architectural improvement. It works by comparing your branch against target branches to generate context-rich output.

Yes, automated code review can analyze diffs against testnet, staging, or main branches. The process builds context by comparing your current branch history with these target branches to identify potential issues and suggest improvements.

Yes, you need the git command-line interface and access to your branch history for diff generation. The tool requires this CLI access to analyze your changes and generate the context-rich diff output needed for pre-review preparation.

The best way to identify code cleanup areas before a human review is to run an automated pre-analysis that flags cosmetic changes, potential problems, and architectural improvement opportunities. This provides a head start by suggesting initial fixes from the git diff.

Automated code review for pull request preparation is limited to analyzing git diffs and branch history. It cannot replace human judgment on complex architectural decisions, but it effectively identifies cosmetic changes and suggests initial code improvements.