.claude/skills/update-provider-models/SKILL.md
# Update Provider Models Update the built-in model configurations for pair-review's AI providers. This skill guides you through checking each provider's CLI for available models, gathering recommendations, and updating the source code. ## When to Use Run this skill periodically (e.g., monthly) or when new model releases are announced for any of the supported AI providers. Skip providers that were recently updated. ## Providers to Update The providers are defined in `src/ai/` with these file
npx skillsauth add in-the-loop-labs/pair-review .claude/skills/update-provider-modelsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Update the built-in model configurations for pair-review's AI providers. This skill guides you through checking each provider's CLI for available models, gathering recommendations, and updating the source code.
Run this skill periodically (e.g., monthly) or when new model releases are announced for any of the supported AI providers. Skip providers that were recently updated.
The providers are defined in src/ai/ with these files:
gemini-provider.js - Google Gemini CLI modelscodex-provider.js - OpenAI Codex CLI modelscopilot-provider.js - GitHub Copilot CLI modelscursor-agent-provider.js - Cursor Agent CLI modelsopencode-provider.js - OpenCode CLI (no built-in models, config-only)claude-provider.js - Anthropic Claude CLI modelspi-provider.js - Pi coding agent modelsEach provider file has a *_MODELS array at the top defining models with:
id: The CLI model identifier (passed to --model flag)name: Display name in the UItier: One of fast, balanced, thorough (or free, premium)tagline, description, badge, badgeClass: UI metadatadefault: true: Marks the default model for the providerRead ~/.pair-review/config.json to see if any provider commands are overridden.
Look at providers.<id>.command for each provider.
For each provider, run:
<cli> --version
Using the command from config if overridden. Skip providers whose CLI is not installed.
Each CLI has different model listing commands:
gemini -m gemini-2.5-flash -o text 'What models are available?'--list-models flag. Check docs at developers.openai.com/codex/models/ or use web searchcopilot -p 'list available models' (non-interactive) or check docs.github.com/en/copilot/reference/ai-models/supported-modelsagent --list-models — works great, comprehensive outputopencode models — lists all models in provider/model-id format (shows bundled + provider models)claude --help or check docs at code.claude.com/docs/en/cli-referencepi --list-models — shows comprehensive table with provider, model, context, max-out, thinking, images columns.For CLIs that are authenticated, ask them directly:
<cli> -p 'Given these available models: [list], recommend the best for each code review tier:
1. FAST: Quick surface-level review (cheap, fast)
2. BALANCED: Standard PR review (quality/cost ratio)
3. THOROUGH: Deep architectural review (most capable)
Recommend 1 model per tier and explain WHY for code review specifically.'
Also use web search to check:
For each provider, update:
*_MODELS array with new/changed model definitionsdefault: true)getDefaultModel() static method return valueAfter updating, run the test suite to ensure no regressions:
npm test
Leave changes uncommitted for the user to review.
~/.pair-review/config.json under providers.opencode.models/settings for preview features that unlock newer modelsdevelopment
Fetch human review comments from pair-review and make code changes to address them. Use when the user says "address review feedback", "fix review comments", "address comments", or wants to iterate on code based on feedback left by a human reviewer in pair-review.
development
Open outstanding GitHub review requests in pair-review for AI-powered code review. Finds open PRs where my review is pending from the past week and starts pair-review analysis for each. Use when the user says "review requests", "review my PRs", "check review requests", "open review requests", "pair-review my requests", or wants to batch-review their outstanding GitHub review requests.
tools
Open the GitHub pull request for the current branch in the pair-review web UI. This only opens the browser — it does not run AI analysis or generate suggestions. Once open, the user can browse the diff, leave comments, and trigger analysis from the web UI themselves. Use when the user says "review this PR", "review pull request", "open PR review", or wants to open a pair-review session for the current branch's pull request. If the user wants automated AI analysis of the PR rather than just opening the browser, use the `code-critic:analyze` skill (standalone, requires code-critic plugin) or `pair-review:analyze` skill (requires MCP server) instead. Note that the user can also trigger AI analysis from within the pair-review web UI after opening it.
tools
Open local uncommitted changes for review in the pair-review web UI. This only opens the browser — it does not run AI analysis or generate suggestions. Once open, the user can browse the diff, leave comments, and trigger analysis from the web UI themselves. Use when the user says "review my local changes", "review local", "open local review", or wants to open a pair-review session for uncommitted work in the current directory. If the user wants automated AI analysis of their local changes rather than just opening the browser, use the `code-critic:analyze` skill (standalone, requires code-critic plugin) or `pair-review:analyze` skill (requires MCP server) instead. Note that the user can also trigger AI analysis from within the pair-review web UI after opening it.