@in-the-loop-labs/pair-review 1.6.2 → 2.0.1

package/README.md

@@ -10,6 +10,35 @@
 
 ![pair-review screenshot](https://raw.githubusercontent.com/in-the-loop-labs/pair-review/main/docs/screenshot.png)
 
+## Table of Contents
+
+- [What is pair-review?](#what-is-pair-review)
+- [Why pair-review?](#why-pair-review)
+- [Workflows](#workflows)
+  - [Local Review](#1-local-review-human-reviews-agent-generated-code)
+  - [Meta-Review](#2-meta-review-judging-ai-suggestions)
+  - [AI-Guided Review](#3-ai-guided-review-when-youre-accountable)
+- [Quick Start](#quick-start)
+- [Command Line Interface](#command-line-interface)
+- [Configuration](#configuration)
+  - [Environment Variables](#environment-variables)
+  - [GitHub Token](#github-token)
+  - [AI Provider Configuration](#ai-provider-configuration)
+- [Features](#features)
+  - [Three-Level AI Analysis](#three-level-ai-analysis)
+  - [Analysis Configuration](#analysis-configuration)
+  - [Chat](#chat)
+  - [Customization](#customization)
+  - [Review Feedback Export](#review-feedback-export)
+  - [Inline Comments](#inline-comments)
+  - [Local Mode](#local-mode)
+- [Claude Code Plugins](#claude-code-plugins)
+- [MCP Integration](#mcp-integration)
+- [Development](#development)
+- [FAQ](#faq)
+- [Contributing](#contributing)
+- [License](#license)
+
 ## What is pair-review?
 
 pair-review is a local web application for keeping humans in the loop with AI coding agents. Calling it an AI code review tool would be accurate but incomplete — it supports multiple workflows beyond automated review, from reviewing agent-generated code before committing, to judging AI suggestions instead of reading every line, to using AI to guide your attention during a thorough review. You pick what fits your situation.
@@ -365,10 +394,6 @@ The CLI command used for a provider follows this precedence (highest to lowest):
 2. Config file `providers.<provider>.command`
 3. Built-in default
 
-#### Migration Notes
-
-If you have an older config file using `provider` and `model` keys at the top level, they are automatically treated as `default_provider` and `default_model`. No migration is required.
-
 ## Features
 
 ### Three-Level AI Analysis
@@ -381,6 +406,51 @@ pair-review's AI analysis system examines your code changes at increasing levels
 
 This progressive approach keeps analysis focused while catching issues at every scope.
 
+### Analysis Configuration
+
+There are three ways to configure which models run your analysis, each building on the last:
+
+**Single Model** — Pick one provider and model. All enabled analysis levels run with that model, and consolidation uses the same model. The simplest option.
+
+**Review Council** — Pick multiple provider+model combinations that all run in parallel across the selected analysis levels. You pick a separate consolidation model that merges everything together.
+
+- Each reviewer can have its own timeout, instructions, and prompt tier (see [Model Tiers](#model-tiers))
+- Results consolidate first across levels for each reviewer, then across reviewers
+- Individual reviewer results are available alongside the overall council result
+
+**Advanced** — For each enabled analysis level, pick different provider+model combinations. Level 1 might use a fast model while Level 3 uses a thorough one. Supports the same per-model options as Review Council (timeout, instructions, tier). Consolidation model is selected separately. Results consolidate first within each level (if multiple reviewers), then across levels.
+
+The key difference from Review Council is consolidation order: Advanced consolidates within each level first, then across levels, so there are no per-reviewer rollups.
+
+**Example use cases:**
+
+- **Large changesets with Opus 4.6**: Use review council instructions to tell the model to use a Team — it will spawn sub-agents to divide the work
+- **Multi-model parallel review**: Give each model a specific focus area (security, performance, correctness) via per-model instructions and get combined results
+- **Cross-model perspectives**: Run the same analysis across different providers (e.g., Claude, Gemini, GPT) — where models agree signals high-confidence findings, but unique outliers from a single model can be equally valuable, catching issue types that only that model excels at spotting
+
+### Chat
+
+Chat with a full coding agent while you review — it can read the codebase, answer questions, and interact with pair-review on your behalf. Powered by [Pi](https://github.com/mariozechner/pi-coding-agent).
+
+**What you can do:**
+
+- Ask questions about the code, architecture, or intent behind changes
+- Have the agent pull related code into the diff panel as context files — see how changed code connects to the rest of the codebase without leaving the review
+- Adopt, dismiss, or discuss AI suggestions directly from the conversation
+- Create and edit review comments through chat
+- Trigger new analysis runs with custom instructions
+- Start conversations from context — an analysis run, an AI suggestion, a comment, any line or file
+
+**Setup:**
+
+```bash
+npm install -g @mariozechner/pi-coding-agent
+```
+
+Configure your preferred models in `providers.pi.models` — see [AI Provider Configuration](#ai-provider-configuration) for details. Everything else in pair-review works without Pi installed.
+
+**Keyboard shortcut:** Press `p` then `c` to toggle the chat panel.
+
 ### Customization
 
 Tailor AI analysis to your team's standards and your current needs:
@@ -638,6 +708,9 @@ A: OpenCode has no built-in models, so you must configure them in your `~/.pair-
 **Q: How do I use Pi as my AI provider?**
 A: Like OpenCode, Pi has no built-in models. Configure them in your `~/.pair-review/config.json` by adding a `providers.pi.models` array with at least one model definition. Pi supports many providers (Google, Anthropic, OpenAI, etc.) via its `--provider` and `--model` flags. See the [AI Provider Configuration](#ai-provider-configuration) section and `config.example.json` for examples.
 
+**Q: Why does chat use Pi instead of Claude or other providers?**
+A: Pi provides persistent interactive sessions with a full agent — it can read files and run commands in the context of the codebase. Pi is model-agnostic and uses your existing provider subscriptions — no separate API keys needed.
+
 ## Contributing
 
 Contributions welcome! Please:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@in-the-loop-labs/pair-review",
-  "version": "1.6.2",
+  "version": "2.0.1",
   "description": "Your AI-powered code review partner - Close the feedback loop with AI coding agents",
   "main": "src/server.js",
   "bin": {

package/plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "pair-review",
-  "version": "1.6.2",
+  "version": "2.0.1",
   "description": "pair-review app integration — Open PRs and local changes in the pair-review web UI, run server-side AI analysis, and address review feedback. Requires the pair-review MCP server.",
   "author": {
     "name": "in-the-loop-labs",

package/plugin/skills/review-requests/SKILL.md

@@ -35,7 +35,10 @@ Each result provides `number`, `title`, `html_url`, and `repo` (as `owner/repo`)
 
 ### Phase 3: Open each PR in pair-review with auto-analysis
 
-For each PR found, open it in the browser with the `?analyze=true` query parameter, which
+**Limit**: Open at most **5** PRs. If more than 5 are found, open only the first 5 (most
+recently updated) and report how many were skipped.
+
+For each PR found (up to the limit), open it in the browser with the `?analyze=true` query parameter, which
 automatically starts AI analysis when the page loads:
 
 ```

package/plugin-code-critic/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "code-critic",
-  "version": "1.6.2",
+  "version": "2.0.1",
   "description": "AI-powered code review analysis — Run three-level AI analysis and implement-review-fix loops directly in your coding agent. Works standalone, no server required.",
   "author": {
     "name": "in-the-loop-labs",

package/plugin-code-critic/skills/analyze/SKILL.md

@@ -104,12 +104,13 @@ Push the orchestrated JSON to the pair-review web UI so suggestions appear inlin
 2. **Build the POST body** from the orchestrated output:
    - For local mode: set `path` (absolute working directory from `pwd`) and `headSha` (from `git rev-parse HEAD`)
    - For PR mode: set `repo` (`owner/repo`) and `prNumber`
-   - Include `provider`, `model`, `summary`, `suggestions`, and `fileLevelSuggestions` from the orchestrated JSON
+   - Set `provider` and `model` to describe what ran the analysis (e.g., the AI provider and model used)
+   - Include `summary`, `suggestions`, and `fileLevelSuggestions` from the orchestrated JSON
 
-3. **POST via `curl`** to `${SERVER_URL}/api/analysis-results`:
+3. **POST via `curl`** to `${SERVER_URL}/api/analyses/results`:
    ```
    curl -s --connect-timeout 3 --max-time 10 \
-     -X POST "${SERVER_URL}/api/analysis-results" \
+     -X POST "${SERVER_URL}/api/analyses/results" \
      -H "Content-Type: application/json" \
      -d @- <<'PAYLOAD'
    { ... }