What this PR does

Before this PR:
The gh-pr-review skill was a simple single-agent PR review workflow using the gh-pr-review CLI extension (EurFelux/gh-pr-review) for structured inline comments. It only supported PR reviews.

After this PR:
The gh-pr-review skill is a comprehensive code review system inspired by Tencent/tgfx's .codebuddy/skills/cr, adapted for Claude Code's Agent tool. It now supports:

• Multiple review modes: local branch changes, PRs, commits, commit ranges, and file paths
• Multi-agent teams review: parallel reviewer agents with an adversarial verifier agent to reduce false positives
• Risk-based auto-fix: automatic fixing of low/medium/high risk issues based on user-selected mode
• Structured checklists: code and document review checklists tailored for the project's TypeScript/React/Electron stack, with cross-references to vercel-react-best-practices for deeper React/performance analysis
• Self-diagnosis: /gh-pr-review diag to analyze and improve the skill itself
• Checklist evolution: mechanism to add new checklist items based on recurring patterns
• PR review via gh-pr-review extension: retains the gh-pr-review CLI extension for pending reviews with inline comments, preview, and structured submission

Why we need it and why it was done in this way

The previous skill was limited to PR-only review. The tgfx approach provides a battle-tested, comprehensive review system with adversarial verification (reviewer finds issues, verifier challenges them), which significantly reduces false positives.

The following tradeoffs were made:

• Adapted CodeBuddy's CreateTeam/SendMessage/TeamDelete APIs to Claude Code's Agent tool with parallel subagents
• Code checklist adapted for this project's specific stack (TypeScript, React 19, Electron 38, Redux Toolkit, Dexie, AI SDK v5) instead of tgfx's C++ focus
• Cross-references vercel-react-best-practices skill for React/performance checks instead of duplicating those rules
• Added v2 refactoring block rules in judgment matrix (Redux state shape / IndexedDB schema changes always deferred)
• Retained gh-pr-review CLI extension for PR review comment submission (pending review API with preview)

The following alternatives were considered:

• Creating a new /cr skill alongside gh-pr-review — rejected because both serve code review and having two review skills would be confusing

Links to places where the discussion took place:

• Reference implementation: https://github.com/Tencent/tgfx/tree/main/.codebuddy/skills/cr

Breaking changes

None. The skill name and invocation (/gh-pr-review) remain the same. The gh-pr-review CLI extension is still used for PR reviews. New capabilities (local review, teams review, auto-fix) are additive.

Special notes for your reviewer

• The new skill routes to different reference files based on context (PR number, uncommitted changes, branch state, agent teams availability)
• references/teams-review.md is the most complex file — it orchestrates multi-agent review with 6 phases
• All reference files are adapted from tgfx's implementation with project-specific customizations
• Code checklist cross-references vercel-react-best-practices skill for React/performance deep checks

Checklist

• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Documentation: A user-guide update was considered and is present (link) or not required. Check this only when the PR introduces or changes a user-facing feature or behavior.
• Self-review: I have reviewed my own code (e.g., via /gh-pr-review, gh pr diff, or GitHub UI) before requesting review from others

Release note

NONE