@mechanai/deepreview 2.14.0 → 2.15.0

package/.opencode/agents/deepreview-plan-validator.md

@@ -58,9 +58,9 @@ Write your validated plan to the output path provided. Use this structure:
 
 ## Fix Plan
 
-### Fix [N]: [Issue Title]
+### Fix [N]: [Issue Title] (full format — critical/warning)
 **File(s):** path/to/file:line
-**Priority:** critical | warning | suggestion
+**Priority:** critical | warning
 **Validation:** approved | revised | rejected
 **Validation notes:** [1-2 sentences: what was checked, what was found]
 **Approach:** [original or revised approach]
@@ -68,6 +68,14 @@ Write your validated plan to the output path provided. Use this structure:
 [Original code if approved, corrected code if revised, "[rejected — see validation notes]" if rejected]
 **Verification:** [from original plan]
 
+### Fix [N]: [Issue Title] (compact format — suggestion)
+**File(s):** path/to/file:line
+**Priority:** suggestion
+**Validation:** approved | revised | rejected
+**Validation notes:** [1-2 sentences: what was checked, what was found]
+**Change:** [Original or corrected instruction; "[rejected — see validation notes]" if rejected]
+**Verification:** [from original plan, if present]
+
 ## Order of Operations
 [Revised if any fixes were rejected or reordering is needed]
 

package/.opencode/agents/deepreview-planner.md

@@ -25,19 +25,22 @@ You will receive a path to a synthesis file. Read it.
 
 ## Documentation Drift handling
 
-If the synthesis contains a "Documentation Drift" section with a batched checklist, consolidate all those items into a **single** fix entry in the plan. Do not create separate fix entries for each documentation item. Use this format:
+If the synthesis contains a "Documentation Drift" section with a batched checklist, consolidate all those items into a **single** fix entry in the plan using compact format. Do not create separate fix entries for each documentation item. Use this format:
 
 ```
 ### Fix [N]: Documentation Updates
+
 **File(s):** [list all affected files]
 **Priority:** suggestion
-**Approach:** Batch update stale/verbose documentation
-**Code changes:**
-[Group changes by file. For each file, show the exact text replacement.]
+**Change:**
+
+- path/to/file1:42 — Replace "old text" with "new text"
+- path/to/file2:18 — Delete stale comment
+- path/to/file3:55 — Replace "old description" with "new description"
 **Verification:** Confirm updated docs match current code behavior
 ```
 
-Critical documentation findings (which appear individually in the "Critical Issues" section, not in "Documentation Drift") should still get their own fix entries.
+Critical documentation findings (which appear individually in the "Critical Issues" section, not in "Documentation Drift") should still get their own fix entries using full format.
 
 ## Quality rules
 
@@ -45,6 +48,15 @@ Critical documentation findings (which appear individually in the "Critical Issu
 - **Stay within scope.** Only fix what the synthesis identifies. Do not add defensive validation, optimize adjacent code, or improve test coverage beyond what the findings require.
 - **Concrete, not aspirational.** Every code change must be copy-pasteable. No pseudocode, no "something like this", no TODOs.
 
+## Format selection
+
+Select the output format for each fix based on its priority:
+
+- **Full format** for `critical` and `warning` fixes — include Approach and Code change blocks
+- **Compact format** for `suggestion` fixes — use a one-line Change instruction instead (e.g., "Replace X with Y", "Delete line N", "Add X after line N")
+
+For batched documentation fixes, the Change field uses a bullet list (one instruction per location).
+
 ## Output format
 
 Write your implementation plan to the output path provided. Use this structure:
@@ -53,22 +65,33 @@ Write your implementation plan to the output path provided. Use this structure:
 # Implementation Plan — [PR/branch] — [date]
 
 ## Summary
+
 [What needs to be fixed and the estimated scope of work]
 
 ## Fix Plan
 
-### Fix [N]: [Issue Title]
+### Fix [N]: [Issue Title] (full format — critical/warning)
+
 **File(s):** path/to/file:line
-**Priority:** critical | warning | suggestion
+**Priority:** critical | warning
 **Approach:** [what to change and why — 1-2 sentences]
 **Code change:**
 [Exact code to replace the problematic code. Use actual variable names, actual logic. Not pseudocode.]
 **Verification:** [what to check after the fix — 1 sentence]
 
+### Fix [N]: [Issue Title] (compact format — suggestion)
+
+**File(s):** path/to/file:line
+**Priority:** suggestion
+**Change:** [One-line instruction: "Replace X with Y" or "Delete lines N-M" or "Add X after line N"]
+**Verification:** [optional — omit if obvious]
+
 ## Order of Operations
+
 [If fixes depend on each other, specify the order. Otherwise: "Fixes are independent — apply in any order."]
 
 ## Risk
+
 [Any fixes that could introduce new issues and what to watch for]
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mechanai/deepreview",
-  "version": "2.14.0",
+  "version": "2.15.0",
   "description": "Multi-agent parallel code/spec review for OpenCode",
   "license": "MIT",
   "repository": {