@in-the-loop-labs/pair-review 2.0.3 → 2.1.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@in-the-loop-labs/pair-review",
-  "version": "2.0.3",
+  "version": "2.1.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": "2.0.3",
+  "version": "2.1.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-code-critic/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "code-critic",
-  "version": "2.0.3",
+  "version": "2.1.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/references/level1-balanced.md

@@ -92,6 +92,15 @@ Do NOT modify files or run write commands. Analyze and report only.
   "summary": "Brief summary of findings"
 }
 
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+```suggestion
+replacement content here
+```
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
+
 ## Line Number Reference (old_or_new field)
 The "old_or_new" field indicates which line number column to use:
 - **"NEW"** (default): Use the NEW column number for:

package/plugin-code-critic/skills/analyze/references/level1-fast.md

@@ -78,6 +78,15 @@ Annotated diff tool, `cat -n`, ls, find, grep. Do NOT modify files.
   "summary": "Brief summary"
 }
 
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+```suggestion
+replacement content here
+```
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
+
 ## Line Numbers (old_or_new)
 - "NEW" (default): added [+] and context lines
 - "OLD": deleted [-] lines only

package/plugin-code-critic/skills/analyze/references/level1-thorough.md

@@ -138,6 +138,15 @@ Output JSON with this structure:
   "summary": "Brief summary of findings"
 }
 
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+```suggestion
+replacement content here
+```
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
+
 ## Line Number Reference (old_or_new field)
 The "old_or_new" field indicates which line number column to use:
 - **"NEW"** (default): Use the NEW column number. This is correct for:

package/plugin-code-critic/skills/analyze/references/level2-balanced.md

@@ -103,6 +103,15 @@ Note: You may use parallel read-only Tasks to examine multiple files simultaneou
   "summary": "Brief summary of file context findings"
 }
 
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+```suggestion
+replacement content here
+```
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
+
 ## Line Number Reference (old_or_new field)
 - **"NEW"** (default): For ADDED [+] lines and CONTEXT lines
 - **"OLD"**: ONLY for DELETED [-] lines

package/plugin-code-critic/skills/analyze/references/level2-fast.md

@@ -87,6 +87,15 @@ Annotated diff tool (preferred), `cat -n <file>`, ls, find, grep. Do NOT modify
   "summary": "Brief summary"
 }
 
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+```suggestion
+replacement content here
+```
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
+
 ## Line Numbers
 "NEW" (default): added [+] and context lines. "OLD": only deleted [-] lines.
 

package/plugin-code-critic/skills/analyze/references/level2-thorough.md

@@ -177,6 +177,15 @@ Output JSON with this structure:
   "summary": "Brief summary of file context findings"
 }
 
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+```suggestion
+replacement content here
+```
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
+
 ## old_or_new Field Reference
 Use "NEW" (the default) for added lines [+] and context lines. Use "OLD" only for deleted lines [-]. When uncertain, use "NEW".
 

package/plugin-code-critic/skills/analyze/references/level3-balanced.md

@@ -140,6 +140,15 @@ Output JSON with this structure:
   "summary": "Brief summary of how these changes connect to and impact the codebase"
 }
 
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+```suggestion
+replacement content here
+```
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
+
 ## Line Number Reference (old_or_new field)
 The "old_or_new" field indicates which line number column to use:
 - **"NEW"** (default): Use the NEW column number. This is correct for:

package/plugin-code-critic/skills/analyze/references/level3-fast.md

@@ -110,6 +110,15 @@ Output JSON with this structure:
   "summary": "Brief summary of how these changes connect to and impact the codebase"
 }
 
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+```suggestion
+replacement content here
+```
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
+
 ## Line Numbers (old_or_new)
 - **"NEW"** (default): For added lines [+] and context lines
 - **"OLD"**: Only for deleted lines [-]

package/plugin-code-critic/skills/analyze/references/level3-thorough.md

@@ -251,6 +251,15 @@ Output JSON with this structure:
   "summary": "Brief summary of how these changes connect to and impact the codebase"
 }
 
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+```suggestion
+replacement content here
+```
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
+
 ## Line Number Reference (old_or_new field)
 The "old_or_new" field indicates which line number column to use:
 - **"NEW"** (default): Use the NEW column number. This is correct for:

package/plugin-code-critic/skills/analyze/references/orchestration-balanced.md

@@ -120,6 +120,15 @@ Output JSON with this structure:
   "summary": "Brief summary of the key findings and their significance to the reviewer. Focus on WHAT was found, not HOW it was found. Do NOT mention 'orchestration', 'levels', 'merged from Level 1/2/3' etc. Write as if a single reviewer produced this analysis."
 }
 
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+```suggestion
+replacement content here
+```
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
+
 ## Line Number Reference (old_or_new field)
 The "old_or_new" field indicates which line number column to use:
 - **"NEW"** (default): Correct for ADDED lines and CONTEXT lines (unchanged lines in both versions)

package/plugin-code-critic/skills/analyze/references/orchestration-fast.md

@@ -97,6 +97,15 @@ Use "Consider...", "Worth noting..." - guidance not mandates.
   "summary": "Key findings as if from single reviewer (no mention of levels/orchestration)"
 }
 
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+```suggestion
+replacement content here
+```
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
+
 ## old_or_new
 "NEW" (default): added [+] and context lines. "OLD": deleted [-] only. Preserve from input.
 

package/plugin-code-critic/skills/analyze/references/orchestration-thorough.md

@@ -250,6 +250,15 @@ Output JSON with this structure:
   "summary": "Brief summary of the key findings and their significance to the reviewer. Focus on WHAT was found, not HOW it was found. Do NOT mention 'orchestration', 'levels', 'merged from Level 1/2/3' etc. Write as if a single reviewer produced this analysis."
 }
 
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+```suggestion
+replacement content here
+```
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
+
 ## Line Number Reference (old_or_new field)
 The "old_or_new" field indicates which line number column to use:
 - **"NEW"** (default): Use the NEW column number. This is correct for:

package/public/js/components/ChatPanel.js

@@ -2827,7 +2827,7 @@ class ChatPanel {
   _handleDismissCommentClick() {
     if (this.isStreaming || !this._contextItemId) return;
     this._pendingActionContext = { type: 'dismiss-comment', itemId: this._contextItemId };
-    this.inputEl.value = 'Please delete this comment.';
+    this.inputEl.value = 'Please dismiss this comment.';
     this.sendMessage();
   }
 

package/src/ai/analyzer.js

@@ -3505,8 +3505,12 @@ File-level suggestions should NOT have a line number. They apply to the entire f
         continue;
       }
 
+      const suggestionText = suggestion.suggestion;
+      const hasSuggestionBlock = suggestionText?.trimStart().startsWith('```suggestion');
       const body = suggestion.description +
-        (suggestion.suggestion ? '\n\n**Suggestion:** ' + suggestion.suggestion : '');
+        (suggestionText
+          ? (hasSuggestionBlock ? '\n\n' + suggestionText : '\n\n**Suggestion:** ' + suggestionText)
+          : '');
 
       const isFileLevel = suggestion.is_file_level === true || suggestion.line_start === null ? 1 : 0;
       const side = suggestion.old_or_new === 'OLD' ? 'LEFT' : 'RIGHT';

package/src/ai/prompts/baseline/consolidation/balanced.js

@@ -118,6 +118,15 @@ Output JSON with this structure:
   }],
   "summary": "Brief consolidation summary. Write as if a single reviewer produced this analysis — do NOT mention 'consolidation', 'merging', or 'multiple reviewers'."
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true">

package/src/ai/prompts/baseline/consolidation/fast.js

@@ -89,6 +89,15 @@ Merge suggestions from multiple AI reviewers. Deduplicate. Resolve conflicts. Ke
   }],
   "summary": "Key findings as if from single reviewer (no mention of consolidation/merging)"
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true" tier="fast">

package/src/ai/prompts/baseline/consolidation/thorough.js

@@ -173,6 +173,15 @@ Output JSON with this structure:
   }],
   "summary": "Brief summary of the key findings and their significance. Write as if a single reviewer produced this analysis — do NOT mention 'consolidation', 'merging', or 'multiple reviewers'."
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true" tier="thorough">

package/src/ai/prompts/baseline/level1/balanced.js

@@ -119,6 +119,15 @@ Do NOT modify files or run write commands. Analyze and report only.
   }],
   "summary": "Brief summary of findings"
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true">

package/src/ai/prompts/baseline/level1/fast.js

@@ -98,6 +98,15 @@ Annotated diff tool, \`cat -n\`, ls, find, grep. Do NOT modify files.
   }],
   "summary": "Brief summary"
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true" tier="fast">

package/src/ai/prompts/baseline/level1/thorough.js

@@ -161,6 +161,15 @@ Output JSON with this structure:
   }],
   "summary": "Brief summary of findings"
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true" tier="thorough">

package/src/ai/prompts/baseline/level2/balanced.js

@@ -126,6 +126,15 @@ Note: You may use parallel read-only Tasks to examine multiple files simultaneou
   }],
   "summary": "Brief summary of file context findings"
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true">

package/src/ai/prompts/baseline/level2/fast.js

@@ -107,6 +107,15 @@ Annotated diff tool (preferred), \`cat -n <file>\`, ls, find, grep. Do NOT modif
   }],
   "summary": "Brief summary"
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true" tier="fast">

package/src/ai/prompts/baseline/level2/thorough.js

@@ -201,6 +201,15 @@ Output JSON with this structure:
   }],
   "summary": "Brief summary of file context findings"
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true" tier="thorough">

package/src/ai/prompts/baseline/level3/balanced.js

@@ -150,6 +150,15 @@ Output JSON with this structure:
   }],
   "summary": "Brief summary of how these changes connect to and impact the codebase"
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true">

package/src/ai/prompts/baseline/level3/fast.js

@@ -124,6 +124,15 @@ Output JSON with this structure:
   }],
   "summary": "Brief summary of how these changes connect to and impact the codebase"
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true" tier="fast">

package/src/ai/prompts/baseline/level3/thorough.js

@@ -268,6 +268,15 @@ Output JSON with this structure:
   }],
   "summary": "Brief summary of how these changes connect to and impact the codebase"
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true" tier="thorough">

package/src/ai/prompts/baseline/orchestration/balanced.js

@@ -140,6 +140,15 @@ Output JSON with this structure:
   }],
   "summary": "Brief summary of the key findings and their significance to the reviewer. Focus on WHAT was found, not HOW it was found. Do NOT mention 'orchestration', 'levels', 'merged from Level 1/2/3' etc. Write as if a single reviewer produced this analysis."
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true">

package/src/ai/prompts/baseline/orchestration/fast.js

@@ -120,6 +120,15 @@ Use "Consider...", "Worth noting..." - guidance not mandates.
   }],
   "summary": "Key findings as if from single reviewer (no mention of levels/orchestration)"
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true" tier="fast">

package/src/ai/prompts/baseline/orchestration/thorough.js

@@ -283,6 +283,15 @@ Output JSON with this structure:
   }],
   "summary": "Brief summary of the key findings and their significance to the reviewer. Focus on WHAT was found, not HOW it was found. Do NOT mention 'orchestration', 'levels', 'merged from Level 1/2/3' etc. Write as if a single reviewer produced this analysis."
 }
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.
 </section>
 
 <section name="diff-instructions" required="true" tier="thorough">

package/src/ai/prompts/shared/output-schema.js

@@ -148,7 +148,16 @@ function buildOutputSchemaSection(schema) {
 Output ONLY valid JSON with no additional text, explanations, or markdown code blocks. Do not wrap the JSON in \`\`\`json blocks. The response must start with { and end with }.
 
 Output JSON with this structure:
-${JSON.stringify(schema, null, 2)}`
+${JSON.stringify(schema, null, 2)}
+
+### GitHub Suggestion Syntax
+When suggesting a specific change, **embed** a GitHub suggestion block within the "suggestion" field:
+
+\`\`\`suggestion
+replacement content here
+\`\`\`
+
+The content inside the block is the complete replacement for the commented line(s). Do not include explanation inside the block — any explanation should appear as plain text outside it. For non-specific suggestions, use plain text only.`
   };
 }
 

package/src/chat/prompt-builder.js

@@ -44,6 +44,7 @@ function buildChatPrompt({ review, prData, skillPath, chatInstructions }) {
     '- **Comments** are human-curated review findings (created by the reviewer).',
     '- **Suggestions** are AI-generated findings from analysis runs.',
     '- **Workflow**: AI generates suggestions → reviewer triages (adopt, edit, or dismiss) → adopted suggestions become comments.',
+    '- **IMPORTANT**: Do NOT adopt, dismiss, or modify suggestions or comments unless the user explicitly asks you to. Your role is to discuss and explain — the reviewer decides what action to take.',
     '- **Analysis runs** are the process that produces suggestions. Each run has a provider, model, tier, and status.',
     '- **Review ID** is a stable integer identifying this review session, used in all API calls.'
   ];
@@ -69,7 +70,11 @@ function buildChatPrompt({ review, prData, skillPath, chatInstructions }) {
     'These become clickable links in the UI. Do NOT use backtick code spans for file references you want to be clickable.\n\n' +
     'Files in the diff can be referenced freely. Files outside the diff can also be referenced; ' +
     'to make them visible in the diff panel, add them as context files via the API (see skill). ' +
-    'Add context files judiciously — only when directly relevant, with focused line ranges.'
+    'Add context files judiciously — only when directly relevant, with focused line ranges.\n\n' +
+    'When the user asks to see code (e.g. "Show me…", "Where is…", "What does X look like?"), ' +
+    'add the relevant file as a context file with a focused line range so it appears in the diff panel. ' +
+    'When explaining code, prefer referencing specific line ranges (e.g. [[file:path.js:10-25]]) ' +
+    'over quoting large blocks in your response. Short inline snippets (a few lines) are fine when they clarify the explanation.'
   );
 
   // Tool usage discipline — avoid unnecessary Task delegation