Suggest Reviewers Helper

Suggest Reviewers Helper

This skill provides a Python helper script that analyzes git blame data for the /git:suggest-reviewers command. The script handles the complex task of identifying which lines were changed and who authored the original code.

When to Use This Skill

Use this skill when implementing the /git:suggest-reviewers command. The helper script should be invoked during Step 3 of the command implementation (analyzing git blame for changed lines).

DO NOT implement git blame analysis manually - always use the provided analyze_blame.py script.

Prerequisites

• Python 3.6 or higher
• Git repository with commit history
• Git CLI available in PATH

Helper Script: analyze_blame.py

The analyze_blame.py script automates the complex process of:

1. Parsing git diff output to identify specific line ranges that were modified
2. Running git blame on only the changed line ranges (not entire files)
3. Extracting and aggregating author information with statistics
4. Filtering out bot accounts automatically

Usage

For uncommitted changes:

python3 ${GEMINI_EXTENSION_ROOT}/skills/suggest-reviewers/analyze_blame.py \
  --mode uncommitted \
  --file path/to/file1.go \
  --file path/to/file2.py \
  --output json

For committed changes on a feature branch:

python3 ${GEMINI_EXTENSION_ROOT}/skills/suggest-reviewers/analyze_blame.py \
  --mode committed \
  --base-branch main \
  --file path/to/file1.go \
  --file path/to/file2.py \
  --output json

Parameters

• --mode: Required. Either uncommitted or committed

  • uncommitted: Analyzes unstaged/staged changes against HEAD
  • committed: Analyzes committed changes against a base branch

• --base-branch: Required when mode is committed. The base branch to compare against (e.g., main, master)

• --file: Can be specified multiple times. Each file to analyze for blame information. Only changed files should be passed.

• --output: Output format. Default is json. Options:

  • json: Machine-readable JSON output
  • text: Human-readable text output