@gitkraken/core-gitlens 0.6.0 → 0.7.1

package/dist/plus/ai/prompts.js

@@ -1,7 +1,12 @@
-export const generateCommitMessage = {
-    id: 'generate-commitMessage_v2',
-    variables: ['diff', 'context', 'instructions'],
-    template: `You are an advanced AI programming assistant and are tasked with summarizing code changes into a concise but meaningful commit message. You will be provided with a code diff and optional additional context. Your goal is to analyze the changes and create a clear, informative commit message that accurately represents the modifications made to the code
+//#region ../plus/ai/src/prompts.ts
+const generateCommitMessage = {
+	id: "generate-commitMessage_v2",
+	variables: [
+		"diff",
+		"context",
+		"instructions"
+	],
+	template: `You are an advanced AI programming assistant and are tasked with summarizing code changes into a concise but meaningful commit message. You will be provided with a code diff and optional additional context. Your goal is to analyze the changes and create a clear, informative commit message that accurately represents the modifications made to the code
 
 First, examine the following code changes provided in Git diff format:
 <~~diff~~>
@@ -46,12 +51,17 @@ Example output structure:
 
 \${instructions}
 
-Based on the provided code diff and any additional context, create a concise but meaningful commit message following the instructions above`,
+Based on the provided code diff and any additional context, create a concise but meaningful commit message following the instructions above`
 };
-export const generateCreatePullRequest = {
-    id: 'generate-create-pullRequest_v2',
-    variables: ['diff', 'data', 'context', 'instructions'],
-    template: `You are an advanced AI programming assistant and are tasked with summarizing code changes into a concise but meaningful pull request title and description. You will be provided with a code diff and a list of commits. Your goal is to analyze the changes and create a clear, informative title and description that accurately represents the modifications made to the code
+const generateCreatePullRequest = {
+	id: "generate-create-pullRequest_v2",
+	variables: [
+		"diff",
+		"data",
+		"context",
+		"instructions"
+	],
+	template: `You are an advanced AI programming assistant and are tasked with summarizing code changes into a concise but meaningful pull request title and description. You will be provided with a code diff and a list of commits. Your goal is to analyze the changes and create a clear, informative title and description that accurately represents the modifications made to the code
 First, examine the following code changes provided in Git diff format:
 <~~diff~~>
 \${diff}
@@ -101,12 +111,16 @@ Example output structure:
 
 \${instructions}
 
-Based on the provided code diff, commit list, and any additional context, create a concise but meaningful pull request title and body following the instructions above`,
+Based on the provided code diff, commit list, and any additional context, create a concise but meaningful pull request title and body following the instructions above`
 };
-export const generateStashMessage = {
-    id: 'generate-stashMessage_v2',
-    variables: ['diff', 'context', 'instructions'],
-    template: `You are an advanced AI programming assistant and are tasked with creating a concise but descriptive stash message. You will be provided with a code diff of uncommitted changes. Your goal is to analyze the changes and create a clear, single-line stash message that accurately represents the work in progress being stashed
+const generateStashMessage = {
+	id: "generate-stashMessage_v2",
+	variables: [
+		"diff",
+		"context",
+		"instructions"
+	],
+	template: `You are an advanced AI programming assistant and are tasked with creating a concise but descriptive stash message. You will be provided with a code diff of uncommitted changes. Your goal is to analyze the changes and create a clear, single-line stash message that accurately represents the work in progress being stashed
 
 First, examine the following code changes provided in Git diff format:
 <~~diff~~>
@@ -132,12 +146,16 @@ Example output structure:
 
 \${instructions}
 
-Based on the provided code diff, create a concise but descriptive stash message following the instructions above`,
+Based on the provided code diff, create a concise but descriptive stash message following the instructions above`
 };
-export const generateCreateCloudPatch = {
-    id: 'generate-create-cloudPatch_v2',
-    variables: ['diff', 'context', 'instructions'],
-    template: `You are an advanced AI programming assistant and are tasked with summarizing code changes into a concise and meaningful title and description. You will be provided with a code diff and optional additional context. Your goal is to analyze the changes and create a clear, informative title and description that accurately represents the modifications made to the code
+const generateCreateCloudPatch = {
+	id: "generate-create-cloudPatch_v2",
+	variables: [
+		"diff",
+		"context",
+		"instructions"
+	],
+	template: `You are an advanced AI programming assistant and are tasked with summarizing code changes into a concise and meaningful title and description. You will be provided with a code diff and optional additional context. Your goal is to analyze the changes and create a clear, informative title and description that accurately represents the modifications made to the code
 
 First, examine the following code changes provided in Git diff format:
 <~~diff~~>
@@ -179,12 +197,16 @@ Example output structure:
 
 \${instructions}
 
-Based on the provided code diff and any additional context, create a concise but meaningful title and description following the instructions above`,
+Based on the provided code diff and any additional context, create a concise but meaningful title and description following the instructions above`
 };
-export const explainChanges = {
-    id: 'explain-changes',
-    variables: ['diff', 'message', 'instructions'],
-    template: `You are an advanced AI programming assistant and are tasked with creating clear, technical summaries of code changes that help reviewers understand the modifications and their implications. You will analyze a code diff and the author-provided message to produce a structured summary that captures the essential aspects of the changes
+const explainChanges = {
+	id: "explain-changes",
+	variables: [
+		"diff",
+		"message",
+		"instructions"
+	],
+	template: `You are an advanced AI programming assistant and are tasked with creating clear, technical summaries of code changes that help reviewers understand the modifications and their implications. You will analyze a code diff and the author-provided message to produce a structured summary that captures the essential aspects of the changes
 
 First, examine the following code changes provided in Git diff format:
 <~~diff~~>
@@ -233,12 +255,12 @@ Guidelines:
 
 \${instructions}
 
-Based on the provided code diff and message, create a focused technical summary following the format above`,
+Based on the provided code diff and message, create a focused technical summary following the format above`
 };
-export const generateChangelog = {
-    id: 'generate-changelog',
-    variables: ['data', 'instructions'],
-    template: `You are an expert at creating changelogs in the "Keep a Changelog" format (https://keepachangelog.com). Your task is to create a set of clear, informative changelog entries
+const generateChangelog = {
+	id: "generate-changelog",
+	variables: ["data", "instructions"],
+	template: `You are an expert at creating changelogs in the "Keep a Changelog" format (https://keepachangelog.com). Your task is to create a set of clear, informative changelog entries
 
 First, carefully examine the following JSON data containing commit messages and associated issues. The data is structured as an array of "change" objects. Each "change" contains a \`message\` (the commit message) and an \`issues\` array. The \`issues\` array contains objects representing associated issues, each with an \`id\`, \`url\`, and optional \`title\`
 
@@ -281,19 +303,24 @@ Example output structure:
 
 \${instructions}
 
-Based on the provided commit messages and associated issues, create a set of markdown changelog entries following the instructions above. Do not include any explanatory text or metadata`,
+Based on the provided commit messages and associated issues, create a set of markdown changelog entries following the instructions above. Do not include any explanatory text or metadata`
 };
 /** Example output block shared by the {@link generateSearchQuery} template and its structural-retry prompt */
-export const generateSearchQueryExampleJson = `{
+const generateSearchQueryExampleJson = `{
    "query": "[search operators here]",
    "explanation": "[one short sentence describing the interpretation]",
    "mode": "highlight",
    "alternates": []
 }`;
-export const generateSearchQuery = {
-    id: 'generate-searchQuery_v4',
-    variables: ['query', 'date', 'context', 'instructions'],
-    template: `You are an advanced AI assistant that converts natural language queries into structured Git search operators. Your task is to analyze a user's natural language query about their Git repository history and convert it into the appropriate search operators.
+const generateSearchQuery = {
+	id: "generate-searchQuery_v4",
+	variables: [
+		"query",
+		"date",
+		"context",
+		"instructions"
+	],
+	template: `You are an advanced AI assistant that converts natural language queries into structured Git search operators. Your task is to analyze a user's natural language query about their Git repository history and convert it into the appropriate search operators.
 
 Available search operators:
 - 'message:' - Search in commit messages (e.g. 'message:fix bug'); maps to \`git log --extended-regexp --grep=<value>\`
@@ -344,36 +371,48 @@ For complex temporal expressions that might be ambiguous, prefer simpler, more r
 Example output structure:
 ${generateSearchQueryExampleJson}
 
-Return only the JSON object and no other text — no code fences, no explanatory text.`,
+Return only the JSON object and no other text — no code fences, no explanatory text.`
 };
 /** Schema counterpart of the {@link generateSearchQuery} template's described output shape */
-export const generateSearchQuerySchema = {
-    name: 'generate_search_query',
-    schema: {
-        type: 'object',
-        additionalProperties: false,
-        required: ['query', 'explanation', 'mode', 'alternates'],
-        properties: {
-            query: { type: 'string', description: 'The converted search query using the documented operators' },
-            explanation: {
-                type: 'string',
-                description: "One short sentence, in the user's own terms, describing how the query was interpreted",
-            },
-            mode: {
-                type: 'string',
-                enum: ['highlight', 'filter', 'select'],
-                description: 'How the query should be applied: highlight matches, filter to only matches, or select/jump to a specific commit',
-            },
-            alternates: {
-                type: 'array',
-                items: { type: 'string' },
-                description: 'Up to 2 alternative queries for the same intent; empty array if none make sense',
-            },
-        },
-    },
+const generateSearchQuerySchema = {
+	name: "generate_search_query",
+	schema: {
+		type: "object",
+		additionalProperties: false,
+		required: [
+			"query",
+			"explanation",
+			"mode",
+			"alternates"
+		],
+		properties: {
+			query: {
+				type: "string",
+				description: "The converted search query using the documented operators"
+			},
+			explanation: {
+				type: "string",
+				description: "One short sentence, in the user's own terms, describing how the query was interpreted"
+			},
+			mode: {
+				type: "string",
+				enum: [
+					"highlight",
+					"filter",
+					"select"
+				],
+				description: "How the query should be applied: highlight matches, filter to only matches, or select/jump to a specific commit"
+			},
+			alternates: {
+				type: "array",
+				items: { type: "string" },
+				description: "Up to 2 alternative queries for the same intent; empty array if none make sense"
+			}
+		}
+	}
 };
 /** Example output block shared by the {@link generateCommits} template and its structural-retry prompt */
-export const generateCommitsExampleJson = `{
+const generateCommitsExampleJson = `{
    "commits": [
       {
          "message": "[commit message here]",
@@ -382,10 +421,16 @@ export const generateCommitsExampleJson = `{
       }
    ]
 }`;
-export const generateCommits = {
-    id: 'generate-commits_v3',
-    variables: ['hunks', 'existingCommits', 'commitMessages', 'hunkMap', 'instructions'],
-    template: `You are an advanced AI programming assistant tasked with organizing code changes into commits. Your goal is to create a complete set of commits that are related, grouped logically, atomic, and easy to review. You will be working with individual code hunks and may have some existing commits that already have hunks assigned.
+const generateCommits = {
+	id: "generate-commits_v3",
+	variables: [
+		"hunks",
+		"existingCommits",
+		"commitMessages",
+		"hunkMap",
+		"instructions"
+	],
+	template: `You are an advanced AI programming assistant tasked with organizing code changes into commits. Your goal is to create a complete set of commits that are related, grouped logically, atomic, and easy to review. You will be working with individual code hunks and may have some existing commits that already have hunks assigned.
 
 First, examine the following JSON array of code hunks that need to be organized:
 
@@ -467,44 +512,55 @@ Remember:
 \${instructions}
 
 Now, proceed with your analysis and organization of the commits. Return only the JSON object and no other text — no code fences, no XML tags, and no explanatory text.
-`,
+`
 };
 /** Schema counterpart of the {@link generateCommits} template's described output shape */
-export const generateCommitsSchema = {
-    name: 'generate_commits',
-    schema: {
-        type: 'object',
-        additionalProperties: false,
-        required: ['commits'],
-        properties: {
-            commits: {
-                type: 'array',
-                items: {
-                    type: 'object',
-                    additionalProperties: false,
-                    required: ['message', 'explanation', 'hunks'],
-                    properties: {
-                        message: { type: 'string', description: 'The commit message' },
-                        explanation: { type: 'string', description: 'Detailed explanation of the changes' },
-                        hunks: {
-                            type: 'array',
-                            items: {
-                                type: 'object',
-                                additionalProperties: false,
-                                required: ['hunk'],
-                                properties: { hunk: { type: 'integer', description: 'Hunk index from the hunk_map' } },
-                            },
-                        },
-                    },
-                },
-            },
-        },
-    },
+const generateCommitsSchema = {
+	name: "generate_commits",
+	schema: {
+		type: "object",
+		additionalProperties: false,
+		required: ["commits"],
+		properties: { commits: {
+			type: "array",
+			items: {
+				type: "object",
+				additionalProperties: false,
+				required: [
+					"message",
+					"explanation",
+					"hunks"
+				],
+				properties: {
+					message: {
+						type: "string",
+						description: "The commit message"
+					},
+					explanation: {
+						type: "string",
+						description: "Detailed explanation of the changes"
+					},
+					hunks: {
+						type: "array",
+						items: {
+							type: "object",
+							additionalProperties: false,
+							required: ["hunk"],
+							properties: { hunk: {
+								type: "integer",
+								description: "Hunk index from the hunk_map"
+							} }
+						}
+					}
+				}
+			}
+		} }
+	}
 };
-export const startWorkFromIssue = {
-    id: 'start-work-issue',
-    variables: ['issue', 'instructions'],
-    template: `You are an advanced AI programming assistant tasked with helping a developer start work on a new issue. Your goal is to analyze the issue details and provide a clear plan of action, estimate, and implement a solution.
+const startWorkFromIssue = {
+	id: "start-work-issue",
+	variables: ["issue", "instructions"],
+	template: `You are an advanced AI programming assistant tasked with helping a developer start work on a new issue. Your goal is to analyze the issue details and provide a clear plan of action, estimate, and implement a solution.
 
 First, examine the following JSON object containing the issue details:
 
@@ -526,12 +582,12 @@ You can use GitKraken MCP tools to gather additional context about the repositor
 
 \${instructions}
 
-Now, proceed with your analysis and provide a clear plan of action, estimate, and implementation for the issue. Return only the relevant information without any additional text.`,
+Now, proceed with your analysis and provide a clear plan of action, estimate, and implementation for the issue. Return only the relevant information without any additional text.`
 };
-export const reviewPullRequest = {
-    id: 'start-review-pullRequest',
-    variables: ['prData', 'instructions'],
-    template: `You are an advanced AI programming assistant tasked with reviewing a pull request (PR). Your goal is to analyze the PR details and provide a comprehensive review that highlights strengths, identifies potential issues, and suggests improvements.
+const reviewPullRequest = {
+	id: "start-review-pullRequest",
+	variables: ["prData", "instructions"],
+	template: `You are an advanced AI programming assistant tasked with reviewing a pull request (PR). Your goal is to analyze the PR details and provide a comprehensive review that highlights strengths, identifies potential issues, and suggests improvements.
 
 First, examine the following JSON object containing the PR details:
 
@@ -554,14 +610,18 @@ You can use GitKraken MCP tools to gather additional context about the repositor
 
 \${instructions}
 
-Now, proceed with your analysis and provide a comprehensive review of the PR. Return only the relevant information without any additional text.`,
+Now, proceed with your analysis and provide a comprehensive review of the PR. Return only the relevant information without any additional text.`
 };
-// Shared by the reviewChanges and reviewDetail templates so line-citation rules can't drift apart
 const lineCitationGuidance = `- For "lines", copy the "start" and "end" numbers from the \`[NNNNN]\` annotations of the specific lines your finding concerns. Do not count, infer, or estimate — use only the annotated numbers. Removed lines (blank brackets \`[     ]\`) cannot be cited; pick the nearest surrounding new-file line instead. Anchor the range tightly to the lines the finding actually concerns; do not span an entire hunk. If a finding is not tied to specific lines, set "lines" to null; if not tied to a single file, set "file" to null`;
-export const reviewChanges = {
-    id: 'review-changes_v2',
-    variables: ['diff', 'message', 'context', 'instructions'],
-    template: `You are an expert code reviewer analyzing a set of code changes. Your goal is to identify meaningful issues — bugs, logic errors, security vulnerabilities, missing error handling, and potential regressions — while ignoring style preferences and linter-level concerns. Focus on problems a careful human reviewer would catch.
+const reviewChanges = {
+	id: "review-changes_v2",
+	variables: [
+		"diff",
+		"message",
+		"context",
+		"instructions"
+	],
+	template: `You are an expert code reviewer analyzing a set of code changes. Your goal is to identify meaningful issues — bugs, logic errors, security vulnerabilities, missing error handling, and potential regressions — while ignoring style preferences and linter-level concerns. Focus on problems a careful human reviewer would catch.
 
 Examine the following code changes in Git diff format. Each non-header line inside a hunk has been annotated with its 1-based new-file line number in a \`[NNNNN]\` block placed immediately after the line-type marker (\` \`, \`+\`, or \`-\`):
   \` [   42] context line\`     // context: exists in both old and new; number = new-file line
@@ -614,79 +674,115 @@ ${lineCitationGuidance}
 
 \${instructions}
 
-Review the changes and return only the JSON object above — no other text, no code fences.`,
+Review the changes and return only the JSON object above — no other text, no code fences.`
 };
-// Nullable so the same schema passes OpenAI strict mode (all properties required, optionals as
-// null-unions) and Anthropic's structured outputs (which allow optionals natively)
 const reviewFindingSchema = {
-    type: 'object',
-    additionalProperties: false,
-    required: ['severity', 'title', 'description', 'file', 'lines'],
-    properties: {
-        severity: { type: 'string', enum: ['critical', 'warning', 'suggestion'] },
-        title: { type: 'string' },
-        description: { type: 'string' },
-        file: { type: ['string', 'null'] },
-        lines: {
-            type: ['object', 'null'],
-            additionalProperties: false,
-            required: ['start', 'end'],
-            properties: { start: { type: 'integer' }, end: { type: 'integer' } },
-        },
-    },
+	type: "object",
+	additionalProperties: false,
+	required: [
+		"severity",
+		"title",
+		"description",
+		"file",
+		"lines"
+	],
+	properties: {
+		severity: {
+			type: "string",
+			enum: [
+				"critical",
+				"warning",
+				"suggestion"
+			]
+		},
+		title: { type: "string" },
+		description: { type: "string" },
+		file: { type: ["string", "null"] },
+		lines: {
+			type: ["object", "null"],
+			additionalProperties: false,
+			required: ["start", "end"],
+			properties: {
+				start: { type: "integer" },
+				end: { type: "integer" }
+			}
+		}
+	}
 };
 function buildReviewResultSchema(name, findings) {
-    return {
-        name: name,
-        schema: {
-            type: 'object',
-            additionalProperties: false,
-            required: ['overview', 'focusAreas'],
-            properties: {
-                overview: { type: 'string' },
-                focusAreas: {
-                    type: 'array',
-                    items: {
-                        type: 'object',
-                        additionalProperties: false,
-                        required: ['label', 'rationale', 'severity', 'files', 'findings'],
-                        properties: {
-                            label: { type: 'string' },
-                            rationale: { type: 'string' },
-                            severity: { type: 'string', enum: ['critical', 'warning', 'suggestion'] },
-                            files: { type: 'array', items: { type: 'string' } },
-                            findings: findings,
-                        },
-                    },
-                },
-            },
-        },
-    };
+	return {
+		name,
+		schema: {
+			type: "object",
+			additionalProperties: false,
+			required: ["overview", "focusAreas"],
+			properties: {
+				overview: { type: "string" },
+				focusAreas: {
+					type: "array",
+					items: {
+						type: "object",
+						additionalProperties: false,
+						required: [
+							"label",
+							"rationale",
+							"severity",
+							"files",
+							"findings"
+						],
+						properties: {
+							label: { type: "string" },
+							rationale: { type: "string" },
+							severity: {
+								type: "string",
+								enum: [
+									"critical",
+									"warning",
+									"suggestion"
+								]
+							},
+							files: {
+								type: "array",
+								items: { type: "string" }
+							},
+							findings
+						}
+					}
+				}
+			}
+		}
+	};
 }
 /** Schema counterpart of the {@link reviewChanges} template's output shape */
-export const reviewResultSchema = buildReviewResultSchema('review_result', {
-    type: ['array', 'null'],
-    items: reviewFindingSchema,
+const reviewResultSchema = buildReviewResultSchema("review_result", {
+	type: ["array", "null"],
+	items: reviewFindingSchema
 });
 /** Schema counterpart of the {@link reviewOverview} template — the manifest-only pass has no diffs,
- *  so the grammar itself forbids findings (the template mandates `"findings": null`) */
-export const reviewOverviewSchema = buildReviewResultSchema('review_overview', { type: 'null' });
+*  so the grammar itself forbids findings (the template mandates `"findings": null`) */
+const reviewOverviewSchema = buildReviewResultSchema("review_overview", { type: "null" });
 /** Schema counterpart of the {@link reviewDetail} template's output shape */
-export const reviewDetailSchema = {
-    name: 'review_detail',
-    schema: {
-        type: 'object',
-        additionalProperties: false,
-        required: ['findings'],
-        properties: {
-            findings: { type: 'array', items: reviewFindingSchema },
-        },
-    },
+const reviewDetailSchema = {
+	name: "review_detail",
+	schema: {
+		type: "object",
+		additionalProperties: false,
+		required: ["findings"],
+		properties: { findings: {
+			type: "array",
+			items: reviewFindingSchema
+		} }
+	}
 };
-export const reviewOverview = {
-    id: 'review-overview_v2',
-    variables: ['files', 'message', 'context', 'instructions'],
-    template: `You are an expert code reviewer performing an initial assessment of a set of code changes. You are given a file manifest (not full diffs) — use the file paths, change types, and line counts to identify which areas deserve closer inspection.
+const reviewOverview = {
+	id: "review-overview_v2",
+	variables: [
+		"files",
+		"message",
+		"context",
+		"instructions"
+	],
+	template: `You are an expert code reviewer performing an initial assessment of a set of code changes. You are given a file manifest (not full diffs) — use the file paths, change types, and line counts to identify which areas deserve closer inspection.
 
 File manifest (JSON array of changed files):
 <~~files~~>
@@ -725,12 +821,12 @@ Guidelines:
 
 \${instructions}
 
-Assess the changes and return only the JSON object above — no other text, no code fences.`,
+Assess the changes and return only the JSON object above — no other text, no code fences.`
 };
-export const reviewRefine = {
-    id: 'review-refine_v2',
-    variables: ['instructions'],
-    template: `The user has follow-up guidance for the review you produced above. Produce an updated review that incorporates it:
+const reviewRefine = {
+	id: "review-refine_v2",
+	variables: ["instructions"],
+	template: `The user has follow-up guidance for the review you produced above. Produce an updated review that incorporates it:
 - Keep prior findings that remain valid — do not drop them just because the guidance doesn't mention them
 - Update or remove findings the guidance invalidates or de-prioritizes
 - Add any new findings the guidance surfaces
@@ -740,12 +836,17 @@ export const reviewRefine = {
 \${instructions}
 </~~instructions~~>
 
-Produce the full updated review as a single JSON object in the same structure as your previous response. Return only the JSON object — no other text, no code fences.`,
+Produce the full updated review as a single JSON object in the same structure as your previous response. Return only the JSON object — no other text, no code fences.`
 };
-export const addressReviewFindings = {
-    id: 'address-review-findings',
-    variables: ['reviewMarkdown', 'scopeLabel', 'granularity', 'instructions'],
-    template: `You are an AI coding agent tasked with addressing the issues identified in a code review. Your goal is to understand each finding and, where appropriate, propose or make the code changes needed to fix it.
+const addressReviewFindings = {
+	id: "address-review-findings",
+	variables: [
+		"reviewMarkdown",
+		"scopeLabel",
+		"granularity",
+		"instructions"
+	],
+	template: `You are an AI coding agent tasked with addressing the issues identified in a code review. Your goal is to understand each finding and, where appropriate, propose or make the code changes needed to fix it.
 
 The review was performed against: \${scopeLabel}
 
@@ -763,12 +864,19 @@ Guidelines:
 - If a finding is ambiguous, contradicts the surrounding code's intent, or is already addressed in the current state, say so explicitly rather than fabricating a fix.
 - If a finding is out of scope (touches unrelated systems, requires significant refactoring, or contradicts established patterns), surface that as a tradeoff rather than acting on it.
 
-\${instructions}`,
+\${instructions}`
 };
-export const reviewDetail = {
-    id: 'review-detail_v2',
-    variables: ['diff', 'overview', 'message', 'focusArea', 'context', 'instructions'],
-    template: `You are an expert code reviewer performing a detailed inspection of specific files that were flagged for closer review. You have the context from an initial overview assessment.
+const reviewDetail = {
+	id: "review-detail_v2",
+	variables: [
+		"diff",
+		"overview",
+		"message",
+		"focusArea",
+		"context",
+		"instructions"
+	],
+	template: `You are an expert code reviewer performing a detailed inspection of specific files that were flagged for closer review. You have the context from an initial overview assessment.
 
 Initial overview of the full changeset:
 <~~overview~~>
@@ -817,6 +925,9 @@ ${lineCitationGuidance}
 
 \${instructions}
 
-Inspect the diff for this focus area and return only the JSON object above — no other text, no code fences.`,
+Inspect the diff for this focus area and return only the JSON object above — no other text, no code fences.`
 };
+//#endregion
+export { addressReviewFindings, explainChanges, generateChangelog, generateCommitMessage, generateCommits, generateCommitsExampleJson, generateCommitsSchema, generateCreateCloudPatch, generateCreatePullRequest, generateSearchQuery, generateSearchQueryExampleJson, generateSearchQuerySchema, generateStashMessage, reviewChanges, reviewDetail, reviewDetailSchema, reviewOverview, reviewOverviewSchema, reviewPullRequest, reviewRefine, reviewResultSchema, startWorkFromIssue };
+
 //# sourceMappingURL=prompts.js.map