code-review-phase-0-gather-the-diff

You can gather a unified diff for code review by automating the retrieval of version control changes. This skill executes git diff commands to collect the unified diff for the current branch or a specified pull request.

Yes, you can include uncommitted changes when gathering a git diff for review. The skill automatically detects and incorporates uncommitted modifications, ensuring that all local changes are present in the unified diff output.

You can get the diff for a specific pull request or branch by specifying your custom review targets. The skill allows you to pass specific PR numbers, branch names, or file paths to collect the exact unified diff needed.

Yes, you need a local git repository to automate diff gathering. This skill requires access to a git repository and the ability to execute git commands in your software development environment to retrieve the unified diff.

The best way to automate the initial step of a code review process is to use a diff gathering tool. This skill automatically runs git diff to assemble the unified diff, streamlining the preparation phase for subsequent code analysis.

Yes, diff gathering works with specific file paths in version control. You can specify custom review targets including individual file paths, allowing you to narrow the unified diff output to only the relevant modified files.