pr-review

# PR Code Review (Local) Perform a thorough local code review with full project context - reads source files directly, no API truncation limits. **Announce at start:** "I'm using pr-review skill to review the pull request." ## Usage ``` /pr-review [pr_number] ``` `$ARGUMENTS` may contain an optional PR number and/or `--automation` flag. - Without `--automation`: interactive mode (prompts for confirmation, comment, cleanup) - With `--automation`: non-interactive mode (auto-post comment, auto-delete branch, output machine-readable result) --- ## Steps ### Step 1 - Determine PR Number If `$ARGUMENTS` is non-empty, use it as the PR number. Otherwise run: ```bash gh pr view --json number -q .number ``` If this also fails (not on a PR branch), abort with: > No PR number provided and cannot detect one from the current branch. Usage: `/pr-review <pr_number>` Also parse `--automation` from `$ARGUMENTS`: ```bash AUTOMATION_MODE=false if echo "$ARGUMENTS" | grep -q -- '--automation'; then AUTOMATION_MODE=true fi ``` ### Step 2 - Check CI Status ```bash gh pr view <PR_NUMBER> --json statusCheckRollup \ --jq '.statusCheckRollup[] | {name: .name, status: .status, conclusion: .conclusion}' ``` **Required jobs to check:** - `Code Quality` - `Unit Tests (ubuntu-latest)` - `Unit Tests (macos-14)` - `Unit Tests (windows-2022)` - `Coverage Test` - `i18n-check` (`build-test` is an optional job and is not included in the required check list.) **Special cases:** Skip this ...