chameleon-pr-review

# 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. ## Reviewer discipline This review follows the same discipline a senior reviewer applies (the superpowers `requesting-code-review` skill's `code-reviewer` template): be specific (always `file:line`); explain WHY each finding matters, not just what; never say "looks good" without checking; don't mark a nitpick as BLOCK; never give feedback on code you didn't actually read; and always give a clear verdict with its reasoning. The output leads with the verdict line (Step 4 format) and the one-sentence Verdict Reasoning that carries the superpowers "Ready to merge?" assessment, then the strengths, then the findings — a verdict-first order for the reader who needs the decision immediately, not the template's verdict-last order. Every finding is grounded in chameleon data or a removed hunk line — see the grounding loop below. ## 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) ``` ## The six-phase discipline Every review runs the pipeline the chameleon engine runs at turn end, p...