prr-kit 1.2.3 → 1.4.0

package/README.md

@@ -38,9 +38,137 @@ Then open your IDE in the installed project and use one of these commands to sta
 
 ## How It Works
 
-<p align="center">
-  <img src="docs/assets/how-it-works.svg" alt="How It Works" width="100%"/>
-</p>
+```
+┌─────────────────────────────────────────────────────────┐
+│                    /prr-quick                           │
+│              Load config.yaml                           │
+└───────────────────────┬─────────────────────────────────┘
+                        │
+        ╔═══════════════▼════════════════╗
+        ║       PHASE 1 — SELECT PR      ║
+        ╚═══════════════╤════════════════╝
+                        │
+             ┌──────────▼──────────┐
+             │ 1a. git fetch origin │
+             └──────────┬──────────┘
+                        │
+             ┌──────────▼───────────────┐
+             │ 1b. List open PRs/MRs    │
+             │     + recent branches    │
+             └──────────┬───────────────┘
+                        │
+             ┌──────────▼───────────────┐
+             │ 1c. ⌨️  Select PR/branch  │  ← USER INPUT
+             │     Enter PR# or name    │
+             └──────────┬───────────────┘
+                        │
+             ┌──────────▼──────────┐
+             │ 1d. Load diff        │
+             │     count files/lines│
+             └──────────┬──────────┘
+                        │
+             ┌──────────▼──────────────────────────┐
+             │ 1e. Create session folder            │
+             │     {output}/{date}-{slug}/          │
+             └──────────┬──────────────────────────┘
+                        │
+             ┌──────────▼──────────────────────────┐
+             │ 1f. Generate diffs/ folder           │
+             │     one .md per changed file         │
+             └──────────┬──────────────────────────┘
+                        │
+        ╔═══════════════▼════════════════╗
+        ║      PHASE 2 — DESCRIBE PR     ║
+        ╚═══════════════╤════════════════╝
+                        │
+             ┌──────────▼──────────────┐
+             │ 2a. Classify PR type     │
+             │     bugfix/feature/...   │
+             └──────────┬──────────────┘
+                        │
+             ┌──────────▼──────────────┐
+             │ 2b. File-by-file         │
+             │     walkthrough          │
+             └──────────┬──────────────┘
+                        │
+             ┌──────────▼──────────────┐
+             │ 2c. Print PR description │
+             └──────────┬──────────────┘
+                        │
+        ╔═══════════════▼═══════════════════════╗
+        ║   PHASE 2.5 — COLLECT PR CONTEXT      ║
+        ╚═══════════════╤═══════════════════════╝
+                        │
+             ┌──────────▼──────────────────────────┐
+             │ Step 1. Analyze changed files        │
+             │  detect stacks, domains, file types  │
+             └──────────┬──────────────────────────┘
+                        │
+             ┌──────────▼──────────────────────────┐
+             │ Step 2. Collect context from:        │
+             │  CLAUDE.md · CONTRIBUTING.md         │
+             │  .eslintrc · tsconfig · pyproject    │
+             │  ARCHITECTURE.md · docs/**           │
+             │  @context/@security annotations      │
+             │  stack rules (vue3/react/django/...)  │
+             │  MCP tools · RAG · URL sources       │
+             └──────────┬──────────────────────────┘
+                        │
+             ┌──────────▼──────────────────────────┐
+             │ Step 3. ⌨️  User instructions        │  ← USER INPUT
+             │  scope / focus / requirements /      │
+             │  context — or Enter for full review  │
+             └──────────┬──────────────────────────┘
+                        │
+               ┌────────┴────────┐
+               ▼                 ▼
+          [provided]         [empty]
+        parse scope &      scope = "all"
+        focus/req/ctx      full standard
+               │                 │
+               └────────┬────────┘
+                        │
+             ┌──────────▼──────────────────────────┐
+             │ Step 4. Build pr-context.yaml        │
+             │  all collected context + user_instr  │
+             │  → {session_output}/pr-context.yaml  │
+             └──────────┬──────────────────────────┘
+                        │
+        ╔═══════════════▼════════════════╗
+        ║       PHASE 3 — REVIEW         ║
+        ╚═══════════════╤════════════════╝
+                        │
+             ┌──────────▼──────────────────────────┐
+             │ Scope gate                           │
+             │ read user_instructions.review_scope  │
+             └──────┬───────────────────────────────┘
+                    │
+         ┌──────────┴──────────┐
+    [in scope]           [not in scope]
+         │                     │
+         ▼                     ▼
+  ┌─────────────┐        ⏭️ skipped
+  │  GR · SR    │        (no output file)
+  │  PR · AR    │
+  │     BR      │
+  └──────┬──────┘
+         │
+        ╔▼════════════════════════╗
+        ║  PHASE 4 — REPORT       ║
+        ╚╤════════════════════════╝
+         │
+         │  Compile findings → sort by severity
+         │  🔴 Blockers → 🟡 Warnings
+         │  🟢 Suggestions → ❓ Questions
+         │  Write → final-review.md
+         │
+        ╔▼════════════════════════╗
+        ║  PHASE 5 — DONE         ║
+        ╚╤════════════════════════╝
+         │
+         ├── auto_post_comment: true  → post inline comments automatically
+         └── auto_post_comment: false → ⌨️  type PC to post, Enter to finish
+```
 
 The framework installs into your project as a `_prr/` folder. Agents and workflows are Markdown/YAML files that your AI IDE reads and executes — no server, no background process, no API keys required beyond your IDE's AI.
 
@@ -48,25 +176,72 @@ The framework installs into your project as a `_prr/` folder. Agents and workflo
 
 The installer handles configuration interactively — no manual file editing required. During `npx prr-kit install`, you'll be prompted for your name, language, output folder, target repo, and platform.
 
-All values are written automatically to `_prr/prr/config.yaml`:
+All values are written to `_prr/prr/config.yaml`. Full schema overview:
 
 ```yaml
-user_name: YourName
-communication_language: English
-target_repo: .
-platform: auto                        # auto-detect from git remote
-platform_repo: "owner/repo"           # optional — needed for PR listing and inline comments
-review_output: /abs/path/_prr-output/reviews
+# ─── Identity ──────────────────────────────────────────────────────────────
+user_name: YourName                    # Your name — used in review reports
+communication_language: English        # Any language: English | Vietnamese | Japanese | French | …
 
-context_collection:
-  enabled: true
-  mode: pr-specific                   # always fresh, never cached
+# ─── Project ───────────────────────────────────────────────────────────────
+project_name: my-project               # Display name in reports (cosmetic only)
+target_repo: .                         # Path to git repo (. = current dir, or ../other-repo)
+
+# ─── Platform ──────────────────────────────────────────────────────────────
+platform: auto                         # auto | github | gitlab | azure | bitbucket | none
+platform_repo: "owner/repo"           # owner/repo slug — required for PR listing + inline comments
+                                       # leave blank for local-only mode (git diff only)
 
+# ─── Output ────────────────────────────────────────────────────────────────
+review_output: ./_prr-output/reviews   # Where review reports + context files are written
+auto_post_comment: false               # true → auto-post findings after every review (skips PC prompt)
+
+# ─── Context Collection ────────────────────────────────────────────────────
+context_collection:
+  enabled: true                        # false → disable context collection entirely
+  mode: pr-specific                    # only value: pr-specific (always fresh, never cached)
+
+  # Sources below are auto-detected — override only if needed:
+  # primary_sources:  [CLAUDE.md, AGENTS.md, .github/CLAUDE_CODE_RULES.md, .clauderules]
+  # config_files:     [.eslintrc*, .prettierrc*, tsconfig.json, vite.config.*, webpack.config.*, …]
+  # standards_docs:   [CONTRIBUTING.md, ARCHITECTURE.md, docs/**/*.md]
+  # inline_annotations: { enabled: true, patterns: [@context:, @security:, @pattern:, @rule:] }
+
+# ─── External Sources ──────────────────────────────────────────────────────
+# MCP tools + RAG systems available in your AI IDE session.
+# Agent auto-discovers tools and maps them to declared intents.
 external_sources:
-  enabled: false                      # set true to activate MCP + RAG enrichment
+  enabled: false                       # true → activate MCP + RAG enrichment
+
+  mcp:
+    enabled: true                      # toggle MCP independently of master switch
+    intents:                           # what kinds of context to fetch via MCP tools
+      - knowledge_base                 # Confluence, Notion → team standards, ADRs
+      - project_management             # Jira, Linear → linked issue + acceptance criteria
+      - design                         # Figma, Zeplin → design specs (UI PRs only)
+      # - code_intelligence            # Sourcegraph → similar patterns
+    hints:
+      branch_issue_pattern: "([A-Z]+-\\d+)"  # regex to extract issue key from branch name
+                                              # e.g. feature/ENG-123-auth → ENG-123
+
+  rag:
+    enabled: false                     # true → query RAG systems (vector DB, embeddings)
+    intents:
+      - similar_patterns               # find similar code in the codebase
+      - past_decisions                 # previous review decisions for similar code
+      # - architecture_examples        # embedded architecture docs
+
+  sources: []                          # plain URL sources — always fetched via WebFetch
+  # sources:
+  #   - type: url
+  #     name: Shared ESLint config
+  #     url: https://raw.githubusercontent.com/org/standards/main/eslint.md
+  #   - type: url
+  #     name: Security guidelines
+  #     url: https://wiki.company.com/public/security-standards
 ```
 
-> See **[CONFIGURATION.md](CONFIGURATION.md)** for the full schema reference — including MCP tool intents, RAG systems, inline annotations, and URL sources.
+> See **[CONFIGURATION.md](CONFIGURATION.md)** for detailed explanations, examples, and FAQs.
 
 ## Platform Support
 
@@ -89,11 +264,11 @@ external_sources:
 ### Quick mode — one command, full pipeline
 
 ```
-/prr-quick    or    /prr-master → QR
+/prr-quick
 ```
 
-Runs automatically: **select PR → describe → collect context → 5 reviews → generate report**
-Only pauses once to ask which PR/branch to review.
+Runs automatically: **select PR → describe → collect context → review → report**
+Pauses **twice** for user input: once to select the PR/branch, once for review instructions (scope, focus, requirements — or Enter for a full standard review).
 
 ### Manual mode — step by step
 
@@ -101,11 +276,11 @@ Only pauses once to ask which PR/branch to review.
 |------|---------|-------------|
 | `SP` | Select PR | Fetch latest → list open PRs (via `gh`) or branches → select head + base → load diff |
 | `DP` | Describe PR | Classify PR type, generate summary, file-by-file walkthrough |
-| `GR` | General Review | Logic, naming, readability, DRY, best practices |
+| `GR` | General Review | Logic, naming, readability, DRY, best practices, etc. — adapted to your stack |
 | `SR` | Security Review | OWASP Top 10, secrets, auth, rate limits, injection, etc. — adapted to your project |
 | `PR` | Performance Review | N+1 queries, memory leaks, async patterns, caching, etc. — adapted to your stack |
 | `AR` | Architecture Review | SOLID, layers, coupling, consistency with codebase, etc. — adapted to your architecture |
-| `BR` | Business Review | User impact, business risk, feature completeness, data safety, observability |
+| `BR` | Business Review | User impact, business risk, feature completeness, data safety, observability — adapted to your project |
 | `IC` | Improve Code | Concrete BEFORE/AFTER code suggestions |
 | `AK` | Ask Code | Q&A about specific changes in this PR |
 | `RR` | Generate Report | Compile all findings → Markdown report in `_prr-output/reviews/` |
@@ -147,11 +322,11 @@ Specialist reviewer agents are orchestrated internally by the master agent and p
 
 | Reviewer | Focus | Key questions |
 |---|---|---|
-| 👁️ General (GR) | Code quality | Is the logic correct? Naming clear? DRY? Tests present? |
+| 👁️ General (GR) | Code quality + stack practices | Is the logic correct? Naming clear? DRY? Tests present? *(adapted to your stack)* |
 | 🔒 Security (SR) | OWASP Top 10 + stack threats | XSS? Injection? Secrets exposed? Auth correct? *(adapted to your stack)* |
 | ⚡ Performance (PR) | Efficiency + stack patterns | N+1 queries? Memory leaks? Missing await? *(adapted to your stack)* |
 | 🏗️ Architecture (AR) | Structure + conventions | Layer violations? Coupling? Consistent with codebase? *(adapted to your architecture)* |
-| 💼 Business (BR) | Real-world impact | User impact? Business risk? Feature completeness? Data safe? Observability? |
+| 💼 Business (BR) | Real-world impact | User impact? Business risk? Feature completeness? Data safe? Observability? *(adapted to your project)* |
 
 > Checks are adaptive — each reviewer skips categories not relevant to your project and generates additional checks based on detected stacks, project guidelines, and inline annotations.
 
@@ -168,13 +343,14 @@ All findings use a standard format:
 
 ## Context Collection
 
-After [DP] Describe PR, context is collected **automatically** — no manual step needed:
+After [DP] Describe PR, context is collected **automatically** — then the agent pauses once for your instructions:
 
 1. Analyzes changed files to detect domains (`authentication`, `state-management`, etc.)
 2. Reads relevant config files (`.eslintrc`, `.prettierrc`, `tsconfig.json`) and standards docs (`CONTRIBUTING.md`, `ARCHITECTURE.md`)
 3. Extracts inline `@context:` / `@security:` / `@pattern:` annotations from the diff
 4. Optionally queries **MCP tools** (Confluence, Jira, Figma) and **RAG systems** if configured
-5. Writes `pr-{branch}-context.yaml` — loaded by all reviewers
+5. Asks for **review instructions** — scope (`only security`), focus, requirements, or context. Press Enter for a full standard review
+6. Writes `pr-context.yaml` inside the session folder — loaded by all reviewers
 
 > See [CONFIGURATION.md](CONFIGURATION.md) for MCP intents, RAG setup, and URL sources.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prr-kit",
-  "version": "1.2.3",
+  "version": "1.4.0",
   "description": "AI-driven Pull Request Review Kit — structured agent workflows for thorough, consistent code review",
   "main": "tools/cli/prr-cli.js",
   "bin": {

package/src/core/agents/prr-master.agent.yaml

@@ -48,23 +48,23 @@ agent:
 
     - trigger: "GR or fuzzy match on general-review"
       workflow: "{project-root}/_prr/prr/workflows/3-review/general-review/workflow.yaml"
-      description: "[GR] General Review: Logic, naming, readability, best practices"
+      description: "[GR] General Review: Code quality analysis — adapted to your stack"
 
     - trigger: "SR or fuzzy match on security-review"
       workflow: "{project-root}/_prr/prr/workflows/3-review/security-review/workflow.yaml"
-      description: "[SR] Security Review: OWASP top 10, injection, auth, API key exposure"
+      description: "[SR] Security Review: Security analysis — adapted to your project"
 
     - trigger: "PR or fuzzy match on performance-review"
       workflow: "{project-root}/_prr/prr/workflows/3-review/performance-review/workflow.yaml"
-      description: "[PR] Performance Review: N+1 queries, memory leaks, async patterns, bundle size"
+      description: "[PR] Performance Review: Performance analysis — adapted to your stack"
 
     - trigger: "AR or fuzzy match on architecture-review"
       workflow: "{project-root}/_prr/prr/workflows/3-review/architecture-review/workflow.yaml"
-      description: "[AR] Architecture Review: SOLID, layering, coupling, consistency with codebase"
+      description: "[AR] Architecture Review: Architecture analysis — adapted to your codebase"
 
     - trigger: "BR or fuzzy match on business-review"
       workflow: "{project-root}/_prr/prr/workflows/3-review/business-review/workflow.yaml"
-      description: "[BR] Business Review: User impact, business risk, feature completeness, data safety, observability"
+      description: "[BR] Business Review: Business impact analysis — adapted to your project"
 
     - trigger: "IC or fuzzy match on improve-code"
       workflow: "{project-root}/_prr/prr/workflows/4-improve/improve-code/workflow.yaml"
@@ -82,10 +82,14 @@ agent:
       exec: "{project-root}/_prr/prr/workflows/6-report/post-comments/workflow.md"
       description: "[PC] Post Comments: Post inline review comments to GitHub/GitLab/Azure/Bitbucket PR"
 
+    - trigger: "SS or fuzzy match on select-session or resume-session"
+      exec: "{project-root}/_prr/core/tasks/select-session.md"
+      description: "[SS] Select Session: List past review sessions and resume one"
+
     - trigger: "HH or fuzzy match on help"
       exec: "{project-root}/_prr/core/tasks/help.md"
       description: "[HH] Help: Show review workflow guide and available commands"
 
     - trigger: "CL or fuzzy match on clear or clean or reset"
       exec: "{project-root}/_prr/core/tasks/clear.md"
-      description: "[CL] Clear: Remove context files and/or review reports from output folder"
+      description: "[CL] Clear: Delete one or more past review sessions"

package/src/core/tasks/clear.md

@@ -8,58 +8,41 @@
 
 Read `{project-root}/_prr/prr/config.yaml` to get `review_output` path.
 
-### 2. Scan Output Folder
+### 2. Scan Session Folders
 
-List all files currently in `{review_output}`:
+List all session folders in `{review_output}` (datetime-slug subdirectories):
 
 ```bash
-ls "{review_output}/"
+ls -d "{review_output}"/*/
 ```
 
-Group into three categories:
+Each session folder is named `{YYYY-MM-DD-HHmm}-{slug}` (e.g. `2026-03-02-1430-pr44-feature-auth`).
+Inside each folder are: `pr-context.yaml` (knowledge base) and review `.md` files.
 
-**Context files** (session state + knowledge bases):
-- `current-pr-context.yaml` — active session state (which PR is selected)
-- `pr-*-context.yaml` — per-PR knowledge bases built during context collection
-
-**Intermediate review files** (individual review output, used by [RR] and [PC]):
-- `general-review-*.md`
-- `security-review-*.md`
-- `performance-review-*.md`
-- `architecture-review-*.md`
-- `business-review-*.md`
-- `improve-code-*.md`
-- `pr-description-*.md`
-
-**Review reports** (final compiled reports):
-- `review-*.md` — final review reports generated by [RR]
+Also detect any legacy flat files still directly in `{review_output}/` (pre-session-folder format).
 
 ### 3. Display What Exists
 
-Show the user exactly what will be affected:
+Show the user a summary of each session:
 
 ```
 🗂️ PRR Output — {review_output}
 
-Context files ({n}):
-  • current-pr-context.yaml
-  • pr-feature-auth-...-context.yaml
-  • pr-feature-search-...-context.yaml
-  ... (list all pr-*.yaml)
-
-Intermediate review files ({k}):
-  • general-review-2026-02-21.md
-  • security-review-2026-02-21.md
-  • pr-description-2026-02-21.md
-  ... (list all intermediate review files)
-
-Review reports ({m}):
-  • review-feature-auth-indexeddb-migration-2026-02-21.md
-  • review-feature-add-search-functionality-2026-02-21.md
-  ... (list all review-*.md)
+Session folders ({n}):
+
+  📁 2026-03-02-1430-pr44-feature-auth/
+     Branch: feature/auth  |  PR #44  |  2026-03-02
+     Files: pr-context.yaml, pr-description.md,
+            general-review.md, security-review.md, final-review.md
+
+  📁 2026-03-01-0915-fix-null-pointer/
+     Branch: fix/null-pointer  |  no PR  |  2026-03-01
+     Files: general-review.md
+
+  ... (list all session folders)
 ```
 
-If output folder is already empty or doesn't exist:
+If no session folders exist:
 ```
 ✅ Nothing to clear — output folder is already empty.
 ```
@@ -72,49 +55,32 @@ Ask the user what to clear:
 ```
 What would you like to clear?
 
-  [1] All          — context files + intermediate review files + review reports
-  [2] Context only — clear session state and knowledge bases (keep reports)
-  [3] Reports only — clear intermediate review files + final review reports (keep context)
-  [4] Cancel       — do nothing
+  [1] All sessions      — delete all session folders
+  [2] Select sessions   — choose specific session(s) to delete
+  [3] Cancel            — do nothing
 ```
 
 Wait for user input.
 
-### 5. Execute Deletion
-
-**If [1] All:**
-```bash
-rm -f "{review_output}/current-pr-context.yaml"
-rm -f "{review_output}"/pr-*-context.yaml
-rm -f "{review_output}"/general-review-*.md
-rm -f "{review_output}"/security-review-*.md
-rm -f "{review_output}"/performance-review-*.md
-rm -f "{review_output}"/architecture-review-*.md
-rm -f "{review_output}"/business-review-*.md
-rm -f "{review_output}"/improve-code-*.md
-rm -f "{review_output}"/pr-description-*.md
-rm -f "{review_output}"/review-*.md
+**If [2] Select sessions:** List sessions numbered and ask:
+```
+Which session(s) to delete? (e.g. 1, 3 or 1-3)
 ```
+Wait for response.
+
+### 5. Execute Deletion
 
-**If [2] Context only:**
+**If [1] All sessions:**
 ```bash
-rm -f "{review_output}/current-pr-context.yaml"
-rm -f "{review_output}"/pr-*-context.yaml
+rm -rf "{review_output}"/*/
 ```
 
-**If [3] Reports only:**
+**If [2] Selected sessions:** For each chosen session folder:
 ```bash
-rm -f "{review_output}"/general-review-*.md
-rm -f "{review_output}"/security-review-*.md
-rm -f "{review_output}"/performance-review-*.md
-rm -f "{review_output}"/architecture-review-*.md
-rm -f "{review_output}"/business-review-*.md
-rm -f "{review_output}"/improve-code-*.md
-rm -f "{review_output}"/pr-description-*.md
-rm -f "{review_output}"/review-*.md
+rm -rf "{review_output}/{selected_session_folder}/"
 ```
 
-**If [4] Cancel:**
+**If [3] Cancel:**
 ```
 ❌ Cancelled — nothing was deleted.
 ```
@@ -122,15 +88,14 @@ Stop.
 
 ### 6. Confirm Deletion
 
-Verify files are gone and report:
+Verify folders are gone and report:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ✅ Clear complete
 
 Deleted:
-  🗑️  Context files: {n_ctx} file(s) removed
-  🗑️  Review reports: {n_rpt} file(s) removed
+  🗑️  Sessions removed: {n} folder(s)
 
 Output folder: {review_output}
 Status: clean

package/src/core/tasks/help.md

@@ -21,11 +21,11 @@ Use `/prr-help` anytime for guidance on what to do.
 
 ### Available Reviews
 
-- **[GR] General Reviewer** 👁️ — Logic, naming, readability, DRY, best practices
-- **[SR] Security Reviewer** 🔒 — OWASP Top 10, injection, auth, secrets, API key exposure
-- **[PR] Performance Reviewer** ⚡ — N+1 queries, memory leaks, async patterns, bundle size
-- **[AR] Architecture Reviewer** 🏗️ — SOLID, layering, coupling, consistency, blast radius
-- **[BR] Business Reviewer** 💼 — User impact, business risk, feature completeness, data safety, observability
+- **[GR] General Reviewer** 👁️ — Logic, naming, readability, DRY, best practices, etc. — adapted to your stack
+- **[SR] Security Reviewer** 🔒 — OWASP Top 10, injection, auth, secrets, etc. — adapted to your project
+- **[PR] Performance Reviewer** ⚡ — N+1 queries, memory leaks, async patterns, etc. — adapted to your stack
+- **[AR] Architecture Reviewer** 🏗️ — SOLID, layering, coupling, consistency, etc. — adapted to your architecture
+- **[BR] Business Reviewer** 💼 — User impact, business risk, feature completeness, data safety, etc. — adapted to your project
 
 ### Finding Severity Levels
 
@@ -36,4 +36,5 @@ Use `/prr-help` anytime for guidance on what to do.
 
 ### Utilities
 
-- **[CL] Clear** — Remove context files and/or review reports from output folder. Useful when starting fresh or cleaning up after a session. Choose: All / Context only / Reports only.
+- **[SS] Select Session** — List past review sessions and resume one. Use this at the start of a new conversation to pick up where you left off.
+- **[CL] Clear** — Delete one or more past review session folders. Choose specific sessions or clear all.

package/src/core/tasks/select-session.md

@@ -0,0 +1,94 @@
+# Select Session
+
+**Goal:** List all past PR review sessions and let the user resume one by restoring `session_output` into working context.
+
+## EXECUTION
+
+### 1. Load Config
+
+Read `{project-root}/_prr/prr/config.yaml` to get `review_output` path.
+
+### 2. Scan Session Folders
+
+List all session folders in `{review_output}`:
+
+```bash
+ls -d "{review_output}"/*/
+```
+
+For each session folder, read its contents to build a summary:
+
+```bash
+ls "{review_output}/{session_folder}/"
+```
+
+From the files present, determine:
+- **Branch / PR** — from folder name (e.g. `2026-03-02-1430-pr44-feature-auth` → PR #44, branch `feature/auth`)
+- **Date / Time** — from folder name prefix (`2026-03-02-1430`)
+- **Reviews done** — which `*-review.md` files exist
+- **Has final report** — `final-review.md` exists
+- **Has description** — `pr-description.md` exists
+
+### 3. Display Sessions
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+📂 Review Sessions — {review_output}
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+  [1] 2026-03-02 14:30 — PR #44  feature/auth-login
+      Reviews: DP ✓  GR ✓  SR ✓  RR ✓
+      Report:  final-review.md ✓
+
+  [2] 2026-03-01 09:15 — fix/null-pointer-checkout
+      Reviews: DP ✓  GR ✓
+      Report:  —
+
+  [3] 2026-02-28 17:00 — PR #41  chore/upgrade-deps
+      Reviews: DP ✓  GR ✓  AR ✓  RR ✓
+      Report:  final-review.md ✓
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+If no sessions exist:
+```
+✅ No sessions found in {review_output}.
+   Run [SP] Select PR or [QR] Quick Review to start a new session.
+```
+Then stop.
+
+### 4. Ask User to Select
+
+```
+Select a session to resume (enter number):
+```
+
+**HALT — wait for user response.**
+
+### 5. Restore Session
+
+Set `session_output` = full path of the selected session folder.
+
+Load PR metadata from working context sources available in the session folder:
+- Parse `session_output` folder name to extract: `datetime_prefix`, `pr_number` (if `prN-` prefix), `branch_slug`
+- Read `pr-context.yaml` if it exists — extract `pr_metadata.pr_number`, `pr_metadata.branch`, `pr_metadata.base_branch`
+- Derive `target_branch` and `base_branch` from knowledge base or folder name
+
+**Store in working context:**
+- `session_output` = selected folder path
+- `target_branch`, `base_branch`, `pr_number` = from above
+
+Display:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+✅ Session restored
+
+📁 {session_output}
+   Branch: {target_branch} → {base_branch}
+   PR #:   {pr_number}  (if applicable)
+
+Reviews completed: {list or "none"}
+Ready to continue — run any command from the menu.
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```