@juspay/yama 2.2.1 → 2.3.0

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

@@ -58,12 +58,22 @@ export interface KnowledgeBase {
 /**
  * Request for the learn command
  */
+/**
+ * Controls which storage systems are committed after learning extraction.
+ * - "kb"     — commit only the knowledge base file (existing behavior)
+ * - "memory" — commit only per-repo memory files (via NeuroLink + git push)
+ * - "all"    — commit both knowledge base and per-repo memory
+ */
+export type LearnCommitMode = "kb" | "memory" | "all";
 export interface LearnRequest {
     workspace: string;
     repository: string;
     pullRequestId: number;
     dryRun?: boolean;
+    /** @deprecated Use commitMode instead */
     commit?: boolean;
+    /** Controls which storage systems are committed after extraction */
+    commitMode?: LearnCommitMode;
     summarize?: boolean;
     outputPath?: string;
     outputFormat?: "md" | "json";

package/dist/v2/memory/MemoryManager.d.ts

@@ -0,0 +1,57 @@
+/**
+ * Memory Manager
+ *
+ * Provides per-repository condensed memory configuration for NeuroLink.
+ *
+ * This manager builds the NeuroLink-compatible memory SDK config with
+ * file-based custom storage, so that NeuroLink's generate()/stream() calls
+ * can retrieve and store memory using context.userId as the per-repo key.
+ *
+ * Callers control WHEN memory is read/written via per-call flags:
+ *   memory: { enabled: true, read: true, write: false }
+ *
+ * This avoids noise from operational calls (e.g., fetching PR data)
+ * polluting the condensed memory.
+ *
+ * Storage: file-based (.yama/memory/{workspace}-{repository}.txt) (lowercased)
+ * Condensation: LLM-powered via NeuroLink's built-in Hippocampus
+ */
+import { MemoryConfig } from "../types/config.types.js";
+export declare class MemoryManager {
+    private readonly config;
+    private readonly projectRoot;
+    private readonly aiProvider;
+    private readonly aiModel;
+    constructor(config: MemoryConfig, aiProvider: string, aiModel: string, projectRoot?: string);
+    /**
+     * Resolve the storage directory path (handles both absolute and relative paths).
+     */
+    private resolveStorageDir;
+    /**
+     * Build the NeuroLink-compatible Memory config object.
+     *
+     * Passed to NeuroLink constructor as `conversationMemory.memory`.
+     * NeuroLink internally initializes Hippocampus with our file-based
+     * storage and review-specific condensation prompt.
+     */
+    buildNeuroLinkMemoryConfig(): Record<string, unknown>;
+    /**
+     * Build a deterministic owner ID from workspace and repository.
+     * This value is passed as `context.userId` in generate() calls.
+     */
+    static buildOwnerId(workspace: string, repository: string): string;
+    /**
+     * Commit memory files to the repository if autoCommit is enabled.
+     *
+     * Checks git status for changes in the storagePath directory,
+     * then stages, commits, and pushes. Uses [skip ci] to prevent
+     * infinite CI loops. Never throws — failures are logged and ignored
+     * so they never block the review result.
+     */
+    commitMemoryChanges(): Promise<boolean>;
+    /**
+     * Map an ownerId to a safe file path.
+     */
+    private ownerIdToFilePath;
+}
+//# sourceMappingURL=MemoryManager.d.ts.map

package/dist/v2/memory/MemoryManager.js

@@ -0,0 +1,185 @@
+/**
+ * Memory Manager
+ *
+ * Provides per-repository condensed memory configuration for NeuroLink.
+ *
+ * This manager builds the NeuroLink-compatible memory SDK config with
+ * file-based custom storage, so that NeuroLink's generate()/stream() calls
+ * can retrieve and store memory using context.userId as the per-repo key.
+ *
+ * Callers control WHEN memory is read/written via per-call flags:
+ *   memory: { enabled: true, read: true, write: false }
+ *
+ * This avoids noise from operational calls (e.g., fetching PR data)
+ * polluting the condensed memory.
+ *
+ * Storage: file-based (.yama/memory/{workspace}-{repository}.txt) (lowercased)
+ * Condensation: LLM-powered via NeuroLink's built-in Hippocampus
+ */
+import { readFile, writeFile, mkdir, unlink } from "fs/promises";
+import { existsSync } from "fs";
+import { join, dirname, isAbsolute } from "path";
+import { execFile } from "child_process";
+import { promisify } from "util";
+const execFileAsync = promisify(execFile);
+// ============================================================================
+// Constants
+// ============================================================================
+/**
+ * Condensation prompt tailored for code review memory.
+ * Guides the LLM to retain review patterns, team conventions, and
+ * frequently flagged issues rather than individual PR details.
+ */
+const REVIEW_MEMORY_CONDENSATION_PROMPT = `You are a memory condensation engine for an AI code reviewer called Yama.
+You receive:
+1. OLD_MEMORY: the existing condensed memory for a specific repository (may be empty)
+2. NEW_CONTENT: new information from a recent code review or learning extraction
+
+Your job: merge old memory with the new information into a single condensed summary.
+
+Rules:
+- Output ONLY the condensed memory text, nothing else
+- Maximum {{MAX_WORDS}} words
+- PRIORITIZE retaining (most important first):
+  1. False positive patterns: things the team confirmed are NOT issues
+  2. Team coding conventions and style preferences
+  3. Recurring review themes and common issue categories
+  4. Repository-specific domain knowledge and architecture decisions
+  5. Patterns the AI missed that developers caught
+  6. Review outcome trends (approval rate, common blocking reasons)
+- DROP: individual PR numbers, timestamps, one-off issues, greeting text
+- Keep learnings GENERIC and applicable to future reviews
+- If NEW_CONTENT has nothing worth remembering, return OLD_MEMORY unchanged
+- If both are empty, return empty string`;
+// ============================================================================
+// Manager
+// ============================================================================
+export class MemoryManager {
+    config;
+    projectRoot;
+    aiProvider;
+    aiModel;
+    constructor(config, aiProvider, aiModel, projectRoot) {
+        this.config = config;
+        this.aiProvider = aiProvider;
+        this.aiModel = aiModel;
+        this.projectRoot = projectRoot || process.cwd();
+    }
+    /**
+     * Resolve the storage directory path (handles both absolute and relative paths).
+     */
+    resolveStorageDir() {
+        return isAbsolute(this.config.storagePath)
+            ? this.config.storagePath
+            : join(this.projectRoot, this.config.storagePath);
+    }
+    /**
+     * Build the NeuroLink-compatible Memory config object.
+     *
+     * Passed to NeuroLink constructor as `conversationMemory.memory`.
+     * NeuroLink internally initializes Hippocampus with our file-based
+     * storage and review-specific condensation prompt.
+     */
+    buildNeuroLinkMemoryConfig() {
+        const storageDir = this.resolveStorageDir();
+        return {
+            enabled: true,
+            storage: this.config.storage || {
+                type: "custom",
+                onGet: async (ownerId) => {
+                    const filePath = this.ownerIdToFilePath(storageDir, ownerId);
+                    if (!existsSync(filePath)) {
+                        return null;
+                    }
+                    try {
+                        return await readFile(filePath, "utf-8");
+                    }
+                    catch {
+                        return null;
+                    }
+                },
+                onSet: async (ownerId, memory) => {
+                    const filePath = this.ownerIdToFilePath(storageDir, ownerId);
+                    const dir = dirname(filePath);
+                    if (!existsSync(dir)) {
+                        await mkdir(dir, { recursive: true });
+                    }
+                    await writeFile(filePath, memory, "utf-8");
+                },
+                onDelete: async (ownerId) => {
+                    const filePath = this.ownerIdToFilePath(storageDir, ownerId);
+                    if (existsSync(filePath)) {
+                        await unlink(filePath);
+                    }
+                },
+            },
+            neurolink: this.config.neurolink || {
+                provider: this.aiProvider,
+                model: this.aiModel,
+                temperature: 0.1,
+            },
+            maxWords: this.config.maxWords,
+            prompt: this.config.prompt || REVIEW_MEMORY_CONDENSATION_PROMPT,
+        };
+    }
+    /**
+     * Build a deterministic owner ID from workspace and repository.
+     * This value is passed as `context.userId` in generate() calls.
+     */
+    static buildOwnerId(workspace, repository) {
+        return `${workspace}-${repository}`.toLowerCase();
+    }
+    /**
+     * Commit memory files to the repository if autoCommit is enabled.
+     *
+     * Checks git status for changes in the storagePath directory,
+     * then stages, commits, and pushes. Uses [skip ci] to prevent
+     * infinite CI loops. Never throws — failures are logged and ignored
+     * so they never block the review result.
+     */
+    async commitMemoryChanges() {
+        if (!this.config.autoCommit) {
+            return false;
+        }
+        const storageDir = this.resolveStorageDir();
+        if (!existsSync(storageDir)) {
+            return false;
+        }
+        try {
+            // Check if there are any changes to commit
+            const { stdout: statusOutput } = await execFileAsync("git", ["status", "--porcelain", storageDir], { cwd: this.projectRoot });
+            if (!statusOutput.trim()) {
+                console.log("   🧠 No memory changes to commit");
+                return false;
+            }
+            const commitMessage = this.config.commitMessage ||
+                "chore: update yama review memory [skip ci]";
+            // Stage memory files
+            await execFileAsync("git", ["add", storageDir], {
+                cwd: this.projectRoot,
+            });
+            // Commit with [skip ci] to prevent infinite loops
+            await execFileAsync("git", ["commit", "-m", commitMessage], {
+                cwd: this.projectRoot,
+            });
+            // Push to the current branch
+            await execFileAsync("git", ["push"], {
+                cwd: this.projectRoot,
+            });
+            console.log("   🧠 Memory changes committed and pushed");
+            return true;
+        }
+        catch (error) {
+            console.warn(`   ⚠️ Memory auto-commit failed: ${error.message}`);
+            return false;
+        }
+    }
+    /**
+     * Map an ownerId to a safe file path.
+     */
+    ownerIdToFilePath(storageDir, ownerId) {
+        const safeId = ownerId.replace(/[^a-zA-Z0-9-]/g, "-");
+        return join(storageDir, `${safeId}.md`);
+    }
+}
+//# sourceMappingURL=MemoryManager.js.map

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;
@@ -12,10 +12,12 @@ export interface YamaV2Config {
     descriptionEnhancement: DescriptionEnhancementConfig;
     memoryBank: MemoryBankConfig;
     knowledgeBase: KnowledgeBaseConfig;
+    memory: MemoryConfig;
     projectStandards?: ProjectStandardsConfig;
     monitoring: MonitoringConfig;
     performance: PerformanceConfig;
 }
+export type YamaV2Config = YamaConfig;
 export interface DisplayConfig {
     showBanner: boolean;
     streamingMode: boolean;
@@ -31,6 +33,8 @@ export interface AIConfig {
     enableEvaluation: boolean;
     timeout: string;
     retryAttempts: number;
+    enableToolFiltering?: boolean;
+    toolFilteringMode?: "off" | "log-only" | "active";
     conversationMemory: ConversationMemoryConfig;
 }
 export interface ConversationMemoryConfig {
@@ -111,6 +115,56 @@ export interface KnowledgeBaseConfig {
     /** Auto-commit knowledge base changes (default for --commit flag) */
     autoCommit: boolean;
 }
+/** Storage backend configuration for Hippocampus memory */
+export type MemoryStorageConfig = {
+    type: "sqlite";
+    path?: string;
+} | {
+    type: "redis";
+    host?: string;
+    port?: number;
+    password?: string;
+    db?: number;
+    keyPrefix?: string;
+    ttl?: number;
+} | {
+    type: "s3";
+    bucket: string;
+    prefix?: string;
+} | {
+    type: "custom";
+    onGet: (ownerId: string) => Promise<string | null>;
+    onSet: (ownerId: string, memory: string) => Promise<void>;
+    onDelete: (ownerId: string) => Promise<void>;
+    onClose?: () => Promise<void>;
+};
+/**
+ * Yama-specific memory configuration.
+ * Mirrors NeuroLink's Memory type (HippocampusConfig & { enabled }) with
+ * Yama-specific fields for file-based storage.
+ */
+export interface MemoryConfig {
+    /** Enable per-repo condensed memory feature */
+    enabled: boolean;
+    /** Directory for file-based memory storage (relative to project root) */
+    storagePath: string;
+    /** Maximum word count for condensed memory per repository (default: 50) */
+    maxWords?: number;
+    /** Custom condensation prompt (overrides default review-specific prompt) */
+    prompt?: string;
+    /** Storage backend configuration (default: file-based custom storage managed by Yama) */
+    storage?: MemoryStorageConfig;
+    /** AI provider/model for memory condensation (defaults to main AI provider) */
+    neurolink?: {
+        provider?: string;
+        model?: string;
+        temperature?: number;
+    };
+    /** Auto-commit memory files to the repo after review (default: false) */
+    autoCommit?: boolean;
+    /** Git commit message for memory auto-commits (default: "chore: update yama review memory [skip ci]") */
+    commitMessage?: string;
+}
 export interface ProjectStandardsConfig {
     customPromptsPath: string;
     additionalFocusAreas: FocusArea[];
@@ -138,4 +192,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