chameleon-pr-reviewlisted

# PR Review with Chameleon Context Review code changes against this codebase's actual conventions, principles, and (optionally) the task spec. Combines convention compliance with logic review. ## Input formats ``` /chameleon-pr-review → convention-only review of current branch vs main /chameleon-pr-review PROJ-1234 → full review (conventions + Jira logic check) /chameleon-pr-review <PR-URL> → full review (conventions + linked Jira) /chameleon-pr-review <PR-URL> PROJ-1234 → full review (explicit PR + ticket) ``` ## Execution Follow these steps in order. Do not skip steps. ### Step 1: Parse input Determine what to review: - **No args**: review current branch. Run `git diff main...HEAD --name-only` (or `production...HEAD` if main doesn't exist) to get changed files, then `git diff main...HEAD` (same base) to get the full unified diff. - **Jira key** (matches `[A-Z]+-\d+`): note it for Step 3. - **PR URL** (contains `pullrequests` or `pull`): fetch the PR diff. For Bitbucket, use `bbcurl`. For GitHub, use `gh`. This already returns the full unified diff. - **Both**: use the PR diff and the Jira key. If no changed files found, stop and tell the user. #### 1a. Parse hunks from the unified diff You now hold the full unified diff (not just file names). For each changed file, parse its hunk headers (`@@ -old_start,old_count +new_start,new_count @@`) and record: - **Added/changed line ranges** in the post-change file: the line num