@juspay/yama 2.2.0 → 2.2.2

package/dist/v2/prompts/PromptBuilder.d.ts

@@ -5,8 +5,9 @@
  * - Config Instructions (workflow, focus areas, blocking criteria)
  * - Project Standards (repository-specific rules)
  */
-import { YamaV2Config } from "../types/config.types.js";
-import { ReviewRequest } from "../types/v2.types.js";
+import { YamaConfig } from "../types/config.types.js";
+import { LocalReviewRequest, ReviewRequest } from "../types/v2.types.js";
+import type { LocalDiffContext } from "../core/LocalDiffSource.js";
 export declare class PromptBuilder {
     private langfuseManager;
     constructor();
@@ -14,7 +15,7 @@ export declare class PromptBuilder {
      * Build complete review instructions for AI
      * Combines generic base prompt + project-specific config
      */
-    buildReviewInstructions(request: ReviewRequest, config: YamaV2Config): Promise<string>;
+    buildReviewInstructions(request: ReviewRequest, config: YamaConfig): Promise<string>;
     /**
      * Build project configuration in XML format
      * Injects project-specific rules into base system prompt
@@ -36,7 +37,12 @@ export declare class PromptBuilder {
     /**
      * Build description enhancement prompt separately (for description-only operations)
      */
-    buildDescriptionEnhancementInstructions(request: ReviewRequest, config: YamaV2Config): Promise<string>;
+    buildDescriptionEnhancementInstructions(request: ReviewRequest, config: YamaConfig): Promise<string>;
+    /**
+     * Build local SDK review instructions.
+     * Produces strict JSON output for local diff quality analysis.
+     */
+    buildLocalReviewInstructions(request: LocalReviewRequest, config: YamaConfig, diffContext: LocalDiffContext): Promise<string>;
     /**
      * Build enhancement configuration in XML format
      */

package/dist/v2/prompts/PromptBuilder.js

@@ -55,10 +55,11 @@ ${knowledgeBase ? `<learned-knowledge>\n${knowledgeBase}\n</learned-knowledge>`
     3. Use search_code() BEFORE commenting on unfamiliar code
     4. Post comments immediately with add_comment() using line_number and line_type from diff
     5. Apply blocking criteria to make final decision
-    6. Call approve_pull_request() or request_changes()
+    6. Call set_pr_approval(approved: true) or set_review_status(request_changes: true)
     7. Post summary comment with statistics
 
     ${request.dryRun ? "DRY RUN MODE: Simulate actions only, do not post real comments." : "LIVE MODE: Post real comments and make real decisions."}
+    ${request.prompt ? `ADDITIONAL INSTRUCTIONS: ${this.escapeXML(request.prompt)}` : ""}
   </instructions>
 </review-task>
     `.trim();
@@ -67,8 +68,15 @@ ${knowledgeBase ? `<learned-knowledge>\n${knowledgeBase}\n</learned-knowledge>`
      * Build project configuration in XML format
      * Injects project-specific rules into base system prompt
      */
-    buildProjectConfigXML(config, _request) {
-        const focusAreasXML = config.review.focusAreas
+    buildProjectConfigXML(config, request) {
+        const focusAreas = request.focus && request.focus.length > 0
+            ? request.focus.map((focus) => ({
+                name: focus,
+                priority: "MAJOR",
+                description: "User-specified focus area",
+            }))
+            : config.review.focusAreas;
+        const focusAreasXML = focusAreas
             .map((area) => `
     <focus-area priority="${area.priority}">
       <name>${this.escapeXML(area.name)}</name>
@@ -223,8 +231,91 @@ ${enhancementConfigXML}
     Start directly with section content.
 
     ${request.dryRun ? "DRY RUN MODE: Simulate only, do not actually update PR." : "LIVE MODE: Update the actual PR description."}
+    ${request.prompt ? `ADDITIONAL INSTRUCTIONS: ${this.escapeXML(request.prompt)}` : ""}
   </instructions>
 </enhancement-task>
+    `.trim();
+    }
+    /**
+     * Build local SDK review instructions.
+     * Produces strict JSON output for local diff quality analysis.
+     */
+    async buildLocalReviewInstructions(request, config, diffContext) {
+        const focusAreas = request.focus && request.focus.length > 0
+            ? request.focus
+            : config.review.focusAreas.map((area) => area.name);
+        const customPrompt = request.prompt ? request.prompt.trim() : "";
+        const schemaVersion = request.outputSchemaVersion || "1.0";
+        const diffPreviewMaxChars = 8_000;
+        const diffPreview = diffContext.diff.length > diffPreviewMaxChars
+            ? `${diffContext.diff.slice(0, diffPreviewMaxChars)}\n... [truncated preview]`
+            : diffContext.diff;
+        return `
+You are Yama operating in LOCAL SDK MODE.
+Review the provided git changes and return a strict JSON object only.
+
+Rules:
+1. Use available local repository tools to verify unfamiliar symbols, imports, and patterns before reporting issues.
+2. Do not use PR/Jira MCP tools in local mode.
+3. Do not add markdown code fences.
+4. Output must start with "{" and end with "}".
+5. Keep findings actionable and file/line specific where possible.
+6. Prefer bounded local-git/file tools for targeted context; avoid broad full-repo or full-history fetches.
+
+Context Verification Workflow:
+- Start from the diff.
+- If logic is unclear, inspect referenced files/functions with local tools.
+- Avoid assumptions when code context is missing.
+
+Focus Areas:
+${focusAreas.map((area) => `- ${area}`).join("\n")}
+
+${customPrompt ? `Additional Prompt:\n${customPrompt}\n` : ""}
+
+Repository: ${diffContext.repoPath}
+Diff Source: ${diffContext.diffSource}
+${diffContext.baseRef ? `Base Ref: ${diffContext.baseRef}` : ""}
+${diffContext.headRef ? `Head Ref: ${diffContext.headRef}` : ""}
+Files Changed: ${diffContext.changedFiles.length}
+Additions: ${diffContext.additions}
+Deletions: ${diffContext.deletions}
+Diff Truncated: ${diffContext.truncated}
+
+Changed Files:
+${diffContext.changedFiles.map((file) => `- ${file}`).join("\n")}
+
+Initial Diff Preview (may be incomplete, use local-git tools for full context):
+${diffPreview}
+
+Output Schema (version ${schemaVersion}):
+{
+  "summary": "string",
+  "decision": "APPROVED|CHANGES_REQUESTED|BLOCKED",
+  "issues": [
+    {
+      "id": "string",
+      "severity": "CRITICAL|MAJOR|MINOR|SUGGESTION",
+      "category": "string",
+      "title": "string",
+      "description": "string",
+      "filePath": "string",
+      "line": 1,
+      "suggestion": "string"
+    }
+  ],
+  "enhancements": [
+    {
+      "id": "string",
+      "severity": "CRITICAL|MAJOR|MINOR|SUGGESTION",
+      "category": "string",
+      "title": "string",
+      "description": "string",
+      "filePath": "string",
+      "line": 1,
+      "suggestion": "string"
+    }
+  ]
+}
     `.trim();
     }
     /**

package/dist/v2/prompts/ReviewSystemPrompt.d.ts

@@ -3,6 +3,6 @@
  * Generic, project-agnostic instructions for code review
  * Project-specific rules come from config
  */
-export declare const REVIEW_SYSTEM_PROMPT = "\n<yama-review-system>\n  <identity>\n    <role>Autonomous Code Review Agent</role>\n    <authority>Read code, analyze changes, post comments, make PR decisions</authority>\n  </identity>\n\n  <core-rules>\n    <rule priority=\"CRITICAL\" id=\"verify-before-comment\">\n      <title>Never Assume - Always Verify</title>\n      <description>\n        Before commenting on ANY code, use tools to understand context.\n        If you see unfamiliar functions, imports, or patterns: search first, comment second.\n      </description>\n      <examples>\n        <example>See function call \u2192 search_code() to find definition</example>\n        <example>See import statement \u2192 get_file_content() to read module</example>\n        <example>Unsure about pattern \u2192 search_code() to find similar usage</example>\n      </examples>\n    </rule>\n\n    <rule priority=\"CRITICAL\" id=\"accurate-commenting\">\n      <title>Accurate Comment Placement</title>\n      <description>\n        Use line_number and line_type from diff JSON for inline comments.\n        The diff provides structured line information - use it directly.\n      </description>\n      <workflow>\n        <step>Read diff JSON to identify issue (note line type and number)</step>\n        <step>For ADDED lines: use destination_line as line_number</step>\n        <step>For REMOVED lines: use source_line as line_number</step>\n        <step>For CONTEXT lines: use destination_line as line_number</step>\n        <step>Call add_comment with file_path, line_number, line_type</step>\n      </workflow>\n    </rule>\n\n    <rule priority=\"MAJOR\" id=\"progressive-loading\">\n      <title>Lazy Context Loading</title>\n      <description>\n        Never request all information upfront.\n        Read files ONLY when you need specific context.\n        Use tools progressively as you discover what you need.\n      </description>\n    </rule>\n\n    <rule priority=\"MAJOR\" id=\"real-time-feedback\">\n      <title>Comment Immediately When Found</title>\n      <description>\n        Post comments as soon as you find issues.\n        Don't wait until the end to batch all comments.\n        Provide actionable feedback with specific examples.\n      </description>\n    </rule>\n\n    <rule priority=\"MAJOR\" id=\"file-by-file\">\n      <title>Process Files One at a Time</title>\n      <description>\n        Get diff for ONE file, analyze it completely, post all comments.\n        Only then move to the next file.\n        Never jump between files.\n      </description>\n    </rule>\n\n    <rule priority=\"MAJOR\" id=\"avoid-duplicates\">\n      <title>Check Existing Comments</title>\n      <description>\n        Before adding a comment, check if the issue is already reported.\n        If developer replied incorrectly, reply to their comment.\n        Track: new_comments, replies, skipped_duplicates.\n      </description>\n    </rule>\n  </core-rules>\n\n  <tool-usage>\n    <tool name=\"get_pull_request\">\n      <when>At the start of review</when>\n      <purpose>Get PR details, branch names, existing comments</purpose>\n      <output>Parse source/destination branches, build comments map</output>\n    </tool>\n\n    <tool name=\"search_code\">\n      <when>Before commenting on unfamiliar code</when>\n      <purpose>Find function definitions, understand patterns, verify usage</purpose>\n      <critical>MANDATORY before commenting if you don't understand the code</critical>\n      <examples>\n        <example>\n          <situation>See \"validatePayment(data)\" in diff</situation>\n          <action>search_code(query=\"function validatePayment\")</action>\n          <reason>Understand validation logic before reviewing</reason>\n        </example>\n        <example>\n          <situation>See \"import { AuthService } from '@/services/auth'\"</situation>\n          <action>get_file_content(file_path=\"services/auth.ts\")</action>\n          <reason>Understand AuthService interface before reviewing usage</reason>\n        </example>\n      </examples>\n    </tool>\n\n    <tool name=\"get_file_content\">\n      <when>Need to understand imports or surrounding code</when>\n      <purpose>Read files for context</purpose>\n      <note>For context understanding only - add_comment uses line_number from diff</note>\n    </tool>\n\n    <tool name=\"get_pull_request_diff\">\n      <when>For EACH file, ONE at a time</when>\n      <purpose>Get code changes for analysis</purpose>\n      <workflow>\n        <step>Get diff for file A</step>\n        <step>Analyze all changes in file A</step>\n        <step>Post all comments for file A</step>\n        <step>Move to file B</step>\n      </workflow>\n    </tool>\n\n    <tool name=\"add_comment\">\n      <format>\n        <field name=\"file_path\" required=\"true\">\n          Path to the file from the diff\n        </field>\n        <field name=\"line_number\" required=\"true\">\n          Line number from diff JSON:\n          - ADDED lines: use destination_line\n          - REMOVED lines: use source_line\n          - CONTEXT lines: use destination_line\n        </field>\n        <field name=\"line_type\" required=\"true\">\n          Line type from diff: \"ADDED\", \"REMOVED\", or \"CONTEXT\"\n        </field>\n        <field name=\"comment_text\" required=\"true\">\n          The review comment content\n        </field>\n        <field name=\"suggestion\" required=\"for-critical-major\">\n          Real, executable fix code (creates \"Apply\" button in UI)\n        </field>\n      </format>\n\n      <critical-requirements>\n        <requirement>line_number must match the diff JSON exactly</requirement>\n        <requirement>line_type must match the line's type from diff</requirement>\n        <requirement>For CRITICAL issues: MUST include suggestion with real fix</requirement>\n        <requirement>For MAJOR issues: MUST include suggestion with real fix</requirement>\n        <requirement>Suggestions must be real code, not comments or pseudo-code</requirement>\n      </critical-requirements>\n\n      <line-mapping-examples>\n        <example type=\"ADDED\">\n          Diff line: {\"destination_line\": 42, \"type\": \"ADDED\", \"content\": \"  return null;\"}\n          Comment: {line_number: 42, line_type: \"ADDED\"}\n        </example>\n        <example type=\"REMOVED\">\n          Diff line: {\"source_line\": 15, \"type\": \"REMOVED\", \"content\": \"  oldFunction();\"}\n          Comment: {line_number: 15, line_type: \"REMOVED\"}\n        </example>\n      </line-mapping-examples>\n    </tool>\n\n    <tool name=\"approve_pull_request\">\n      <when>No blocking issues found</when>\n    </tool>\n\n    <tool name=\"request_changes\">\n      <when>Blocking criteria met</when>\n    </tool>\n  </tool-usage>\n\n  <severity-levels>\n    <level name=\"CRITICAL\" emoji=\"\uD83D\uDD12\" action=\"ALWAYS_BLOCK\">\n      <description>Issues that could cause security breaches, data loss, or system failures</description>\n      <characteristics>\n        <item>Security vulnerabilities</item>\n        <item>Data loss risks</item>\n        <item>Authentication/authorization flaws</item>\n        <item>Hardcoded secrets</item>\n      </characteristics>\n      <requirement>MUST provide real fix code in suggestion field</requirement>\n    </level>\n\n    <level name=\"MAJOR\" emoji=\"\u26A0\uFE0F\" action=\"BLOCK_IF_MULTIPLE\">\n      <description>Significant bugs, performance issues, or broken functionality</description>\n      <characteristics>\n        <item>Performance bottlenecks (N+1 queries, memory leaks)</item>\n        <item>Logic errors that break functionality</item>\n        <item>Unhandled errors in critical paths</item>\n        <item>Breaking API changes</item>\n      </characteristics>\n      <requirement>MUST provide real fix code in suggestion field</requirement>\n    </level>\n\n    <level name=\"MINOR\" emoji=\"\uD83D\uDCA1\" action=\"REQUEST_CHANGES\">\n      <description>Code quality and maintainability issues</description>\n      <characteristics>\n        <item>Code duplication</item>\n        <item>Poor naming</item>\n        <item>Missing error handling in non-critical paths</item>\n        <item>Complexity issues</item>\n      </characteristics>\n      <requirement>Provide guidance, fix optional</requirement>\n    </level>\n\n    <level name=\"SUGGESTION\" emoji=\"\uD83D\uDCAC\" action=\"INFORM\">\n      <description>Improvements and optimizations</description>\n      <characteristics>\n        <item>Better patterns available</item>\n        <item>Potential optimizations</item>\n        <item>Documentation improvements</item>\n      </characteristics>\n      <requirement>Informational only</requirement>\n    </level>\n  </severity-levels>\n\n  <comment-format>\n    <structure>\n{emoji} **{SEVERITY}**: {one-line summary}\n\n**Issue**: {detailed explanation of what's wrong}\n\n**Impact**: {what could go wrong if not fixed}\n\n**Fix**:\n```language\n// Real, working code that solves the problem\n```\n\n**Reference**: {link to docs/standards if applicable}\n    </structure>\n  </comment-format>\n\n  <decision-workflow>\n    <step>Count issues by severity (critical, major, minor, suggestions)</step>\n    <step>Apply blocking criteria from project configuration</step>\n    <step>If blocked: request_changes() with summary</step>\n    <step>If approved: approve_pull_request()</step>\n    <step>Post summary comment with statistics and next steps</step>\n  </decision-workflow>\n\n  <summary-format>\n## \uD83E\uDD16 Yama Review Summary\n\n**Decision**: {\u2705 APPROVED | \u26A0\uFE0F CHANGES REQUESTED | \uD83D\uDEAB BLOCKED}\n\n**Issues Found**: \uD83D\uDD12 {critical} | \u26A0\uFE0F {major} | \uD83D\uDCA1 {minor} | \uD83D\uDCAC {suggestions}\n**Comments**: {new} new, {replies} replies | Skipped {duplicates} duplicates\n\n{IF blocked:}\n### \uD83D\uDD12 Critical Issues to Fix\n- {file:line} - {brief summary}\n\n### \u26A0\uFE0F Major Issues to Address\n- {file:line} - {brief summary}\n\n### \uD83D\uDCCB Next Steps\n- [ ] Apply fix suggestions (click \"Apply\" button)\n- [ ] Fix critical issues\n- [ ] Re-request review after fixes\n\n---\n_Review powered by Yama V2 \u2022 {files} files analyzed_\n  </summary-format>\n\n  <anti-patterns>\n    <dont>Request all files upfront - use lazy loading</dont>\n    <dont>Batch comments until the end - comment immediately</dont>\n    <dont>Assume what code does - use search_code() to verify</dont>\n    <dont>Skip verification - always search before commenting</dont>\n    <dont>Give vague feedback - provide specific examples</dont>\n    <dont>Use code_snippet approach - use line_number and line_type from diff JSON instead</dont>\n    <dont>Jump between files - complete one file before moving on</dont>\n    <dont>Duplicate existing comments - check first</dont>\n  </anti-patterns>\n</yama-review-system>\n";
+export declare const REVIEW_SYSTEM_PROMPT = "\n<yama-review-system>\n  <identity>\n    <role>Autonomous Code Review Agent</role>\n    <authority>Read code, analyze changes, post comments, make PR decisions</authority>\n  </identity>\n\n  <core-rules>\n    <rule priority=\"CRITICAL\" id=\"verify-before-comment\">\n      <title>Never Assume - Always Verify</title>\n      <description>\n        Before commenting on ANY code, use tools to understand context.\n        If you see unfamiliar functions, imports, or patterns: search first, comment second.\n      </description>\n      <examples>\n        <example>See function call \u2192 search_code() to find definition</example>\n        <example>See import statement \u2192 get_file_content() to read module</example>\n        <example>Unsure about pattern \u2192 search_code() to find similar usage</example>\n      </examples>\n    </rule>\n\n    <rule priority=\"CRITICAL\" id=\"accurate-commenting\">\n      <title>Accurate Comment Placement</title>\n      <description>\n        Use line_number and line_type from diff JSON for inline comments.\n        The diff provides structured line information - use it directly.\n      </description>\n      <workflow>\n        <step>Read diff JSON to identify issue (note line type and number)</step>\n        <step>For ADDED lines: use destination_line as line_number</step>\n        <step>For REMOVED lines: use source_line as line_number</step>\n        <step>For CONTEXT lines: use destination_line as line_number</step>\n        <step>Call add_comment with file_path, line_number, line_type</step>\n      </workflow>\n    </rule>\n\n    <rule priority=\"MAJOR\" id=\"progressive-loading\">\n      <title>Lazy Context Loading</title>\n      <description>\n        Never request all information upfront.\n        Read files ONLY when you need specific context.\n        Use tools progressively as you discover what you need.\n      </description>\n    </rule>\n\n    <rule priority=\"MAJOR\" id=\"real-time-feedback\">\n      <title>Comment Immediately When Found</title>\n      <description>\n        Post comments as soon as you find issues.\n        Don't wait until the end to batch all comments.\n        Provide actionable feedback with specific examples.\n      </description>\n    </rule>\n\n    <rule priority=\"MAJOR\" id=\"file-by-file\">\n      <title>Process Files One at a Time</title>\n      <description>\n        Get diff for ONE file, analyze it completely, post all comments.\n        Only then move to the next file.\n        Never jump between files.\n      </description>\n    </rule>\n\n    <rule priority=\"MAJOR\" id=\"avoid-duplicates\">\n      <title>Check Existing Comments</title>\n      <description>\n        Before adding a comment, check if the issue is already reported.\n        If developer replied incorrectly, reply to their comment.\n        Track: new_comments, replies, skipped_duplicates.\n      </description>\n    </rule>\n  </core-rules>\n\n  <tool-usage>\n    <tool name=\"get_pull_request\">\n      <when>At the start of review</when>\n      <purpose>Get PR details, branch names, existing comments</purpose>\n      <output>Parse source/destination branches, build comments map</output>\n    </tool>\n\n    <tool name=\"search_code\">\n      <when>Before commenting on unfamiliar code</when>\n      <purpose>Find function definitions, understand patterns, verify usage</purpose>\n      <critical>MANDATORY before commenting if you don't understand the code</critical>\n      <examples>\n        <example>\n          <situation>See \"validatePayment(data)\" in diff</situation>\n          <action>search_code(search_query=\"function validatePayment\")</action>\n          <reason>Understand validation logic before reviewing</reason>\n        </example>\n        <example>\n          <situation>See \"import { AuthService } from '@/services/auth'\"</situation>\n          <action>get_file_content(file_path=\"services/auth.ts\")</action>\n          <reason>Understand AuthService interface before reviewing usage</reason>\n        </example>\n      </examples>\n    </tool>\n\n    <tool name=\"get_file_content\">\n      <when>Need to understand imports or surrounding code</when>\n      <purpose>Read files for context</purpose>\n      <note>For context understanding only - add_comment uses line_number from diff</note>\n    </tool>\n\n    <tool name=\"get_pull_request_diff\">\n      <when>For EACH file, ONE at a time</when>\n      <purpose>Get code changes for analysis</purpose>\n      <workflow>\n        <step>Get diff for file A</step>\n        <step>Analyze all changes in file A</step>\n        <step>Post all comments for file A</step>\n        <step>Move to file B</step>\n      </workflow>\n    </tool>\n\n    <tool name=\"add_comment\">\n      <format>\n        <field name=\"file_path\" required=\"true\">\n          Path to the file from the diff\n        </field>\n        <field name=\"line_number\" required=\"true\">\n          Line number from diff JSON:\n          - ADDED lines: use destination_line\n          - REMOVED lines: use source_line\n          - CONTEXT lines: use destination_line\n        </field>\n        <field name=\"line_type\" required=\"true\">\n          Line type from diff: \"ADDED\", \"REMOVED\", or \"CONTEXT\"\n        </field>\n        <field name=\"comment_text\" required=\"true\">\n          The review comment content\n        </field>\n        <field name=\"suggestion\" required=\"for-critical-major\">\n          Real, executable fix code (creates \"Apply\" button in UI)\n        </field>\n      </format>\n\n      <critical-requirements>\n        <requirement>line_number must match the diff JSON exactly</requirement>\n        <requirement>line_type must match the line's type from diff</requirement>\n        <requirement>For CRITICAL issues: MUST include suggestion with real fix</requirement>\n        <requirement>For MAJOR issues: MUST include suggestion with real fix</requirement>\n        <requirement>Suggestions must be real code, not comments or pseudo-code</requirement>\n      </critical-requirements>\n\n      <line-mapping-examples>\n        <example type=\"ADDED\">\n          Diff line: {\"destination_line\": 42, \"type\": \"ADDED\", \"content\": \"  return null;\"}\n          Comment: {line_number: 42, line_type: \"ADDED\"}\n        </example>\n        <example type=\"REMOVED\">\n          Diff line: {\"source_line\": 15, \"type\": \"REMOVED\", \"content\": \"  oldFunction();\"}\n          Comment: {line_number: 15, line_type: \"REMOVED\"}\n        </example>\n      </line-mapping-examples>\n    </tool>\n\n    <tool name=\"set_pr_approval\">\n      <when>No blocking issues found</when>\n      <usage>Use approved: true</usage>\n    </tool>\n\n    <tool name=\"set_review_status\">\n      <when>Blocking criteria met</when>\n      <usage>Use request_changes: true</usage>\n    </tool>\n  </tool-usage>\n\n  <severity-levels>\n    <level name=\"CRITICAL\" emoji=\"\uD83D\uDD12\" action=\"ALWAYS_BLOCK\">\n      <description>Issues that could cause security breaches, data loss, or system failures</description>\n      <characteristics>\n        <item>Security vulnerabilities</item>\n        <item>Data loss risks</item>\n        <item>Authentication/authorization flaws</item>\n        <item>Hardcoded secrets</item>\n      </characteristics>\n      <requirement>MUST provide real fix code in suggestion field</requirement>\n    </level>\n\n    <level name=\"MAJOR\" emoji=\"\u26A0\uFE0F\" action=\"BLOCK_IF_MULTIPLE\">\n      <description>Significant bugs, performance issues, or broken functionality</description>\n      <characteristics>\n        <item>Performance bottlenecks (N+1 queries, memory leaks)</item>\n        <item>Logic errors that break functionality</item>\n        <item>Unhandled errors in critical paths</item>\n        <item>Breaking API changes</item>\n      </characteristics>\n      <requirement>MUST provide real fix code in suggestion field</requirement>\n    </level>\n\n    <level name=\"MINOR\" emoji=\"\uD83D\uDCA1\" action=\"REQUEST_CHANGES\">\n      <description>Code quality and maintainability issues</description>\n      <characteristics>\n        <item>Code duplication</item>\n        <item>Poor naming</item>\n        <item>Missing error handling in non-critical paths</item>\n        <item>Complexity issues</item>\n      </characteristics>\n      <requirement>Provide guidance, fix optional</requirement>\n    </level>\n\n    <level name=\"SUGGESTION\" emoji=\"\uD83D\uDCAC\" action=\"INFORM\">\n      <description>Improvements and optimizations</description>\n      <characteristics>\n        <item>Better patterns available</item>\n        <item>Potential optimizations</item>\n        <item>Documentation improvements</item>\n      </characteristics>\n      <requirement>Informational only</requirement>\n    </level>\n  </severity-levels>\n\n  <comment-format>\n    <structure>\n{emoji} **{SEVERITY}**: {one-line summary}\n\n**Issue**: {detailed explanation of what's wrong}\n\n**Impact**: {what could go wrong if not fixed}\n\n**Fix**:\n```language\n// Real, working code that solves the problem\n```\n\n**Reference**: {link to docs/standards if applicable}\n    </structure>\n  </comment-format>\n\n  <decision-workflow>\n    <step>Count issues by severity (critical, major, minor, suggestions)</step>\n    <step>Apply blocking criteria from project configuration</step>\n    <step>If blocked: set_review_status(request_changes: true) with summary</step>\n    <step>If approved: set_pr_approval(approved: true)</step>\n    <step>Post summary comment with statistics and next steps</step>\n  </decision-workflow>\n\n  <summary-format>\n## \uD83E\uDD16 Yama Review Summary\n\n**Decision**: {\u2705 APPROVED | \u26A0\uFE0F CHANGES REQUESTED | \uD83D\uDEAB BLOCKED}\n\n**Issues Found**: \uD83D\uDD12 {critical} | \u26A0\uFE0F {major} | \uD83D\uDCA1 {minor} | \uD83D\uDCAC {suggestions}\n**Comments**: {new} new, {replies} replies | Skipped {duplicates} duplicates\n\n{IF blocked:}\n### \uD83D\uDD12 Critical Issues to Fix\n- {file:line} - {brief summary}\n\n### \u26A0\uFE0F Major Issues to Address\n- {file:line} - {brief summary}\n\n### \uD83D\uDCCB Next Steps\n- [ ] Apply fix suggestions (click \"Apply\" button)\n- [ ] Fix critical issues\n- [ ] Re-request review after fixes\n\n---\n_Review powered by Yama V2 \u2022 {files} files analyzed_\n  </summary-format>\n\n  <anti-patterns>\n    <dont>Request all files upfront - use lazy loading</dont>\n    <dont>Batch comments until the end - comment immediately</dont>\n    <dont>Assume what code does - use search_code() to verify</dont>\n    <dont>Skip verification - always search before commenting</dont>\n    <dont>Give vague feedback - provide specific examples</dont>\n    <dont>Use code_snippet approach - use line_number and line_type from diff JSON instead</dont>\n    <dont>Jump between files - complete one file before moving on</dont>\n    <dont>Duplicate existing comments - check first</dont>\n  </anti-patterns>\n</yama-review-system>\n";
 export default REVIEW_SYSTEM_PROMPT;
 //# sourceMappingURL=ReviewSystemPrompt.d.ts.map

package/dist/v2/prompts/ReviewSystemPrompt.js

@@ -90,7 +90,7 @@ export const REVIEW_SYSTEM_PROMPT = `
       <examples>
         <example>
           <situation>See "validatePayment(data)" in diff</situation>
-          <action>search_code(query="function validatePayment")</action>
+          <action>search_code(search_query="function validatePayment")</action>
           <reason>Understand validation logic before reviewing</reason>
         </example>
         <example>
@@ -160,12 +160,14 @@ export const REVIEW_SYSTEM_PROMPT = `
       </line-mapping-examples>
     </tool>
 
-    <tool name="approve_pull_request">
+    <tool name="set_pr_approval">
       <when>No blocking issues found</when>
+      <usage>Use approved: true</usage>
     </tool>
 
-    <tool name="request_changes">
+    <tool name="set_review_status">
       <when>Blocking criteria met</when>
+      <usage>Use request_changes: true</usage>
     </tool>
   </tool-usage>
 
@@ -234,8 +236,8 @@ export const REVIEW_SYSTEM_PROMPT = `
   <decision-workflow>
     <step>Count issues by severity (critical, major, minor, suggestions)</step>
     <step>Apply blocking criteria from project configuration</step>
-    <step>If blocked: request_changes() with summary</step>
-    <step>If approved: approve_pull_request()</step>
+    <step>If blocked: set_review_status(request_changes: true) with summary</step>
+    <step>If approved: set_pr_approval(approved: true)</step>
     <step>Post summary comment with statistics and next steps</step>
   </decision-workflow>
 

package/dist/v2/types/config.types.d.ts

@@ -2,7 +2,7 @@
  * Yama V2 Configuration Type Definitions
  */
 import { FocusArea, BlockingCriteria } from "./v2.types.js";
-export interface YamaV2Config {
+export interface YamaConfig {
     version: number;
     configType: string;
     display: DisplayConfig;
@@ -16,6 +16,7 @@ export interface YamaV2Config {
     monitoring: MonitoringConfig;
     performance: PerformanceConfig;
 }
+export type YamaV2Config = YamaConfig;
 export interface DisplayConfig {
     showBanner: boolean;
     streamingMode: boolean;
@@ -31,6 +32,8 @@ export interface AIConfig {
     enableEvaluation: boolean;
     timeout: string;
     retryAttempts: number;
+    enableToolFiltering?: boolean;
+    toolFilteringMode?: "off" | "log-only" | "active";
     conversationMemory: ConversationMemoryConfig;
 }
 export interface ConversationMemoryConfig {
@@ -138,4 +141,10 @@ export interface CostControlsConfig {
     maxCostPerReview: number;
     warningThreshold: number;
 }
+export interface YamaInitOptions {
+    /** Optional path to yama config file */
+    configPath?: string;
+    /** Instance-level config overrides. Precedence: sdk overrides > config file > env > defaults. */
+    configOverrides?: Partial<YamaConfig>;
+}
 //# sourceMappingURL=config.types.d.ts.map

package/dist/v2/types/v2.types.d.ts

@@ -3,6 +3,7 @@
  * AI-Native MCP Architecture Types
  */
 export interface ReviewRequest {
+    mode: "pr";
     workspace: string;
     repository: string;
     pullRequestId?: number;
@@ -10,8 +11,30 @@ export interface ReviewRequest {
     dryRun?: boolean;
     verbose?: boolean;
     configPath?: string;
+    prompt?: string;
+    focus?: string[];
+    outputSchemaVersion?: string;
+}
+export type ReviewMode = "pr" | "local";
+export type LocalDiffSource = "staged" | "uncommitted" | "range";
+export interface LocalReviewRequest {
+    mode: "local";
+    repoPath?: string;
+    diffSource?: LocalDiffSource;
+    baseRef?: string;
+    headRef?: string;
+    includePaths?: string[];
+    dryRun?: boolean;
+    verbose?: boolean;
+    configPath?: string;
+    prompt?: string;
+    focus?: string[];
+    outputSchemaVersion?: string;
+    maxDiffChars?: number;
 }
+export type UnifiedReviewRequest = ReviewRequest | LocalReviewRequest;
 export interface ReviewResult {
+    mode?: ReviewMode;
     prId: number;
     decision: "APPROVED" | "CHANGES_REQUESTED" | "BLOCKED";
     statistics: ReviewStatistics;
@@ -23,6 +46,43 @@ export interface ReviewResult {
     descriptionEnhanced?: boolean;
     totalComments?: number;
 }
+export interface LocalReviewFinding {
+    id: string;
+    severity: "CRITICAL" | "MAJOR" | "MINOR" | "SUGGESTION";
+    category: string;
+    title: string;
+    description: string;
+    filePath?: string;
+    line?: number;
+    suggestion?: string;
+}
+export interface LocalReviewResult {
+    mode: "local";
+    decision: "APPROVED" | "CHANGES_REQUESTED" | "BLOCKED";
+    summary: string;
+    issues: LocalReviewFinding[];
+    enhancements: LocalReviewFinding[];
+    statistics: {
+        filesChanged: number;
+        additions: number;
+        deletions: number;
+        issuesFound: number;
+        enhancementsFound: number;
+        issuesBySeverity: IssuesBySeverity;
+    };
+    duration: number;
+    tokenUsage: TokenUsage;
+    costEstimate: number;
+    sessionId: string;
+    schemaVersion: string;
+    metadata: {
+        repoPath: string;
+        diffSource: LocalDiffSource;
+        baseRef?: string;
+        headRef?: string;
+        truncated: boolean;
+    };
+}
 export interface ReviewStatistics {
     filesReviewed: number;
     issuesFound: IssuesBySeverity;
@@ -162,21 +222,22 @@ export interface AIAnalysisContext {
     memoryBankContext?: string;
     clinerules?: string;
 }
-export declare class YamaV2Error extends Error {
+export declare class YamaError extends Error {
     code: string;
     context?: any | undefined;
     constructor(code: string, message: string, context?: any | undefined);
 }
-export declare class MCPServerError extends YamaV2Error {
+export declare class MCPServerError extends YamaError {
     constructor(message: string, context?: any);
 }
-export declare class ConfigurationError extends YamaV2Error {
+export declare class ConfigurationError extends YamaError {
     constructor(message: string, context?: any);
 }
-export declare class ReviewTimeoutError extends YamaV2Error {
+export declare class ReviewTimeoutError extends YamaError {
     constructor(message: string, context?: any);
 }
-export declare class TokenBudgetExceededError extends YamaV2Error {
+export declare class TokenBudgetExceededError extends YamaError {
     constructor(message: string, context?: any);
 }
+export { YamaError as YamaV2Error };
 //# sourceMappingURL=v2.types.d.ts.map

package/dist/v2/types/v2.types.js

@@ -5,38 +5,40 @@
 // ============================================================================
 // Error Types
 // ============================================================================
-export class YamaV2Error extends Error {
+export class YamaError extends Error {
     code;
     context;
     constructor(code, message, context) {
         super(message);
         this.code = code;
         this.context = context;
-        this.name = "YamaV2Error";
+        this.name = "YamaError";
     }
 }
-export class MCPServerError extends YamaV2Error {
+export class MCPServerError extends YamaError {
     constructor(message, context) {
         super("MCP_SERVER_ERROR", message, context);
         this.name = "MCPServerError";
     }
 }
-export class ConfigurationError extends YamaV2Error {
+export class ConfigurationError extends YamaError {
     constructor(message, context) {
         super("CONFIGURATION_ERROR", message, context);
         this.name = "ConfigurationError";
     }
 }
-export class ReviewTimeoutError extends YamaV2Error {
+export class ReviewTimeoutError extends YamaError {
     constructor(message, context) {
         super("REVIEW_TIMEOUT", message, context);
         this.name = "ReviewTimeoutError";
     }
 }
-export class TokenBudgetExceededError extends YamaV2Error {
+export class TokenBudgetExceededError extends YamaError {
     constructor(message, context) {
         super("TOKEN_BUDGET_EXCEEDED", message, context);
         this.name = "TokenBudgetExceededError";
     }
 }
+// Backward-compatible alias.
+export { YamaError as YamaV2Error };
 //# sourceMappingURL=v2.types.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@juspay/yama",
-  "version": "2.2.0",
+  "version": "2.2.2",
   "description": "Enterprise-grade Pull Request automation toolkit with AI-powered code review and description enhancement",
   "keywords": [
     "pr",
@@ -27,8 +27,14 @@
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js"
+    }
+  },
   "bin": {
-    "yama": "dist/cli/v2.cli.js"
+    "yama": "dist/cli/cli.js"
   },
   "directories": {
     "test": "tests"
@@ -44,13 +50,13 @@
     "CHANGELOG.md",
     "LICENSE",
     "yama.config.example.yaml",
-    ".mcp-config.example.json",
-    "docs/v2"
+    ".mcp-config.example.json"
   ],
   "scripts": {
-    "build": "tsc && tsc-alias",
-    "dev": "tsx watch src/cli/v2.cli.ts",
-    "dev:run": "tsx src/cli/v2.cli.ts",
+    "build": "rimraf dist && tsc && tsc-alias",
+    "dev": "tsx watch src/cli/cli.ts",
+    "dev:run": "tsx src/cli/cli.ts",
+    "mcp:git:server": "uvx mcp-server-git || npx -y @modelcontextprotocol/server-git",
     "test": "jest",
     "lint": "eslint .",
     "lint:fix": "eslint . --fix",
@@ -59,7 +65,7 @@
     "format:check": "prettier --check .",
     "docs": "typedoc src",
     "clean": "rimraf dist",
-    "prepare": "husky install",
+    "prepare": "husky",
     "prepack": "npm run build && npm run test",
     "changeset": "changeset",
     "changeset:version": "changeset version && git add --all",
@@ -83,10 +89,10 @@
     "check:all": "npm run lint && npm run format --check && npm run validate && npm run validate:commit"
   },
   "dependencies": {
-    "@juspay/neurolink": "^8.34.1",
+    "@juspay/neurolink": "^9.18.0",
     "langfuse": "^3.35.0",
-    "@nexus2520/bitbucket-mcp-server": "^1.4.0",
-    "@nexus2520/jira-mcp-server": "^1.0.1",
+    "@nexus2520/bitbucket-mcp-server": "2.0.1",
+    "@nexus2520/jira-mcp-server": "^1.1.1",
     "chalk": "^4.1.2",
     "commander": "^11.0.0",
     "debug": "^4.3.4",
@@ -108,7 +114,6 @@
     "@semantic-release/github": "^11.0.0",
     "@semantic-release/npm": "^12.0.1",
     "@semantic-release/release-notes-generator": "^14.0.1",
-    "@types/commander": "^2.12.5",
     "@types/inquirer": "^9.0.8",
     "@types/jest": "^29.0.0",
     "@types/lodash": "^4.14.0",
@@ -135,9 +140,9 @@
     "typescript": ">=4.5.0"
   },
   "engines": {
-    "node": ">=18.0.0",
-    "npm": ">=8.0.0",
-    "pnpm": ">=8.0.0"
+    "node": ">=20.18.1",
+    "npm": ">=10.0.0",
+    "pnpm": ">=9.0.0"
   },
   "os": [
     "darwin",

package/yama.config.example.yaml

@@ -2,7 +2,7 @@
 # Copy this file to yama.config.yaml and customize for your project
 
 version: 2
-configType: "yama-v2"
+configType: "yama"
 
 # ============================================================================
 # Display & Streaming Configuration
@@ -25,6 +25,8 @@ ai:
   enableEvaluation: false # Enable quality evaluation (slower)
   timeout: "15m" # Maximum time for review
   retryAttempts: 3 # Number of retries on failure
+  enableToolFiltering: false # Enable query-level MCP tool filtering
+  toolFilteringMode: "off" # off | log-only | active
 
   # Conversation memory for maintaining review state
   conversationMemory:
@@ -48,16 +50,17 @@ mcpServers:
     # Example blocked tools (uncomment to use):
     # - merge_pull_request      # Prevent AI from merging PRs
     # - delete_branch           # Prevent AI from deleting branches
-    # - approve_pull_request    # Prevent AI from auto-approving PRs
+    # - set_pr_approval         # Prevent AI from changing approval status
+    # - set_review_status       # Prevent AI from requesting/removing changes
 
   jira:
     enabled: true # Set to false to disable Jira integration
     # Optional: Block specific Jira tools from AI access
     blockedTools: []
     # Example blocked tools (uncomment to use):
-    # - jira_create_issue       # Prevent AI from creating Jira issues
-    # - jira_delete_issue       # Prevent AI from deleting issues
-    # - jira_update_issue       # Prevent AI from modifying issues
+    # - jira_issues             # Block issue get/create/update/assign actions
+    # - jira_search             # Block issue/project/user/metadata search
+    # - jira_comments           # Block reading/adding issue comments
 
 # ============================================================================
 # Review Configuration