smart-review 1.0.1 → 1.0.2

package/lib/utils/i18n.js

@@ -0,0 +1,986 @@
+// Internationalization utilities: messages, prompt builders, and helpers
+
+// Determine effective locale from config or environment
+export function getLocale(configOrLocale) {
+  const raw = typeof configOrLocale === 'string'
+    ? configOrLocale
+    : (configOrLocale?.locale || process.env.SMART_REVIEW_LOCALE || 'zh-CN');
+  const lower = String(raw).toLowerCase();
+  if (lower.startsWith('en')) return 'en-US';
+  return 'zh-CN';
+}
+
+function format(str, params) {
+  if (!params) return str;
+  return String(str).replace(/\{(\w+)\}/g, (m, k) => (params[k] !== undefined ? String(params[k]) : m));
+}
+
+// Field labels used in AI outputs and parsing
+export const FIELD_LABELS = {
+  'zh-CN': {
+    file: '文件路径：',
+    risk: '风险等级：',
+    reason: '风险原因：',
+    suggestion: '修改建议：',
+    snippet: '代码片段：',
+    content: '代码内容：'
+  },
+  'en-US': {
+    file: 'File Path:',
+    risk: 'Risk Level:',
+    reason: 'Risk Reason:',
+    suggestion: 'Suggestions:',
+    snippet: 'Code Snippet:',
+    content: 'Code Content:'
+  }
+};
+
+// Display risk in target language
+export function displayRisk(risk, localeOrConfig) {
+  const loc = getLocale(localeOrConfig);
+  const DICT_RISK = {
+    'zh-CN': {
+      critical: '致命',
+      high: '高危',
+      medium: '中危',
+      low: '低危',
+      suggestion: '建议'
+    },
+    'en-US': {
+      critical: 'Critical',
+      high: 'High',
+      medium: 'Medium',
+      low: 'Low',
+      suggestion: 'Suggestion'
+    }
+  };
+  const dict = DICT_RISK[loc] || DICT_RISK['en-US'];
+  return dict[risk] || risk;
+}
+
+// Translated message catalog
+const MESSAGES = {
+  'zh-CN': {
+    // Git hook script messages (pre-rendered at install time)
+    hook_header_comment: '智能代码审查 - pre-commit钩子（子项目兼容，基于暂存文件逐层定位）',
+    hook_start_review: '🔍 启动代码审查...',
+    hook_no_staged: '📭 没有暂存的文件需要审查',
+    hook_found_staged_header: '📁 发现暂存文件:',
+    hook_cd_repo_fail: '❌ 无法进入仓库根目录',
+    hook_cmd_not_found1: '❌ 未找到 smart-review。请在对应子项目安装：npm i -D smart-review',
+    hook_cmd_not_found2: '   或在仓库根安装供统一使用：npm i -D smart-review',
+    hook_use_command_prefix: '⚙️  使用命令:',
+    hook_review_fail: '❌ 代码审查未通过，请修复问题后重新提交',
+    hook_review_pass: '✅ 代码审查通过，继续提交',
+
+    // Install
+    install_search_git_root_dbg: '查找Git根目录，从 {dir} 开始...',
+    install_found_git_root_success: '找到Git根目录: {dir}',
+    install_no_git_use_current: 'ℹ️  未找到.git目录，使用当前目录作为项目根目录',
+    install_start: '🚀 开始安装智能代码审查系统...',
+    install_done_success: '🎉 智能代码审查系统安装完成！',
+    install_bundled_info: '💡 系统已内置默认配置和规则，无需额外配置即可使用',
+    install_customize_tip: '📝 如需自定义，请编辑 .smart-review/ 目录下的配置文件',
+    install_failed: '安装失败: {error}',
+    install_create_review_dir: '创建 .smart-review 目录',
+    install_create_ai_rules_dir: '创建 ai-rules 子目录（AI提示词）',
+    install_create_local_rules_dir: '创建 local-rules 子目录（静态规则）',
+    install_create_template_success: '创建 {desc}',
+    install_git_missing: '未检测到 Git，请先安装后重试： {url}',
+    install_init_git_warn: '未检测到 .git 目录，尝试初始化 Git 仓库...',
+    install_init_git_failed: 'Git 仓库初始化失败，跳过钩子安装',
+    install_precommit_installed_success: '安装 pre-commit Git钩子',
+    install_precommit_perm_warn: '无法设置执行权限，但钩子文件已创建',
+    install_test_hook: '🧪 测试Git钩子...',
+    install_test_hook_success: '钩子检测通过',
+    install_hook_missing: '钩子文件不存在',
+    install_hook_perm_dbg: '钩子文件权限: {mode}, 可执行: {exec}',
+    install_hook_perm_fix_warn: '钩子文件不可执行，尝试重新设置权限...',
+    install_hook_perm_check_failed: '无法检查钩子文件权限: {error}',
+    install_optional_header: '📝 可选配置:',
+    install_optional_item1: '1. 编辑 .smart-review/smart-review.json 配置AI参数和风险等级',
+    install_optional_item2: '2. 在 .smart-review/local-rules/ 目录添加静态规则文件',
+    install_optional_item3: '3. 在 .smart-review/ai-rules/ 目录添加AI提示词文件',
+    install_optional_item4: '4. 设置 OPENAI_API_KEY 环境变量启用AI审查',
+    install_paths_header: '⚙️  配置文件位置:',
+    install_local_rules_path: '静态规则: {path}',
+    install_ai_rules_path: 'AI提示词: {path}',
+    install_test_header: '🔧 测试命令:',
+    install_test_git_commit: 'git add . && git commit -m "test"  # 测试提交触发审查',
+    install_test_cli: 'npx smart-review --files test/src/test-file.js  # 手动测试审查（使用项目内CLI）',
+    // System prompt templates
+    system_prompt_template: '你是一个资深代码审查与优化专家。\n\n请严格按照以下格式返回每个问题，每个问题使用开始/结束标记包裹，并以空行分隔：\n{start}\n{Lfile}{绝对文件路径}\n{Lsnippet}{具体的代码片段；如片段中存在每行的[n]前缀，请原样保留}\n{Lrisk}{致命/高危/中危/低危/建议}\n{Lreason}{详细原因}\n{Lsuggestion}{具体的修改建议（允许多行）}\n{end}\n\n约束：\n- 必须包含绝对文件路径与具体片段；禁止使用文字行号或行范围（如“第X行/第X-Y行”）。\n- 如片段存在每行的[n]前缀，请原样保留。\n- 由于预处理（剥离注释、忽略无需审查片段），片段中的[n]源行号可能不连续，这是正常的，严格忽略“行号跳跃/行号不连续”等现象，不得作为问题或风险原因。\n- 重点关注安全、性能、代码质量、架构设计。',
+    diff_system_prompt_template: '你负责Git变更的增量审查，仅审查新增行（+）。删除行（-）与上下文仅用于理解。\n\n请严格按照以下格式返回每个问题：\n{start}\n{Lfile}{绝对文件路径}\n{Lsnippet}{新增的具体代码片段，去除+号前缀；如存在每行的[n]前缀，请原样保留}\n{Lrisk}{致命/高危/中危/低危/建议}\n{Lreason}{说明新增代码可能引入的问题}\n{Lsuggestion}{针对新增代码的具体修改建议}\n{end}\n\n说明：\n- 片段只包含新增代码（不含+前缀），允许保留[n]行号前缀。\n- 忽略由预处理或增量片段带来的行号不连续。',
+    // CLI
+    cli_start: '代码审查启动中，请等待...',
+    debug_enabled: '通过命令行参数启用调试日志模式',
+    ai_disabled: '通过命令行参数禁用AI分析',
+    ai_enabled: '通过命令行参数启用AI分析',
+    diff_only_enabled: '通过命令行参数启用Git Diff增量审查模式',
+    usage_header: '使用方法:',
+    usage_staged: '  npx smart-code-reviewer --staged    # 审查暂存区文件',
+    usage_diffonly: '  npx smart-code-reviewer --staged --diff-only  # 仅审查暂存区变动内容(git diff)',
+    usage_files: '  npx smart-code-reviewer --files file1,file2  # 审查指定文件',
+    review_error: '审查执行失败: {error}',
+
+    // Config loader
+    external_config_parse_failed_warn: '外部配置文件解析失败，使用默认配置: {error}',
+    use_external_rules_only_info: '使用外部规则模式：仅加载 local-rules 目录中的规则',
+    load_external_rules_failed_warn: '加载外部规则失败: {error}',
+    temp_file_method_failed_fallback_info: '临时文件方法失败，回退到 base64 方法: {error}',
+    load_rule_file_failed_warn: '加载规则文件失败 {file}: {error}',
+
+    // Reviewer
+    review_staged_start: '开始审查暂存区代码...',
+    using_diff_mode: '🔍 使用Git Diff增量审查模式 - 仅审查变动内容',
+    using_full_mode: '📁 使用全文件审查模式',
+    no_staged_files: '📭 暂存区没有文件需要审查',
+    found_staged_files_n: '📁 发现 {count} 个文件需要审查',
+    get_staged_failed: '获取暂存区文件失败: {error}',
+    review_specific_start: '开始审查指定文件: {files}',
+    file_not_exists: '文件不存在: {path}',
+    start_git_diff_mode: '🔍 启动Git Diff增量审查模式...',
+    no_changes_skip: '📝 暂存区无变更内容，跳过审查',
+    found_changed_files_n: '📊 发现 {count} 个变更文件，开始增量审查...',
+    // Merge/Rebase filters
+    merge_rebase_detected_info: '🔀 检测到 Git 合并/变基过程，按策略过滤审查文件',
+    merge_conflict_paths_found_n: '⚔️  冲突文件 {count} 个，仅审查这些文件',
+    merge_rebase_no_conflict_skip: '✅ 合并/变基期间未检测到冲突文件，跳过审查',
+    apply_static_rules_dbg: '应用静态规则检查...',
+    static_rules_found_n_dbg: '静态规则发现 {count} 个问题',
+    file_skipped_by_type: '文件已跳过审查: {path} (文件类型被忽略)',
+    blocking_risk_detected_skip_ai: '发现阻断等级风险 ({levels})，跳过AI分析',
+    blocking_risk_terminate: '发现阻断等级风险，终止审查流程',
+    ai_start_n_files: '🤖 开始AI智能分析 {count} 个文件...',
+    ai_diff_failed: 'AI分析文件变更失败 {path}: {error}',
+    git_diff_done: '✨ Git Diff增量审查完成',
+    git_diff_error: 'Git Diff审查过程出错: {error}',
+    smart_segmentation_done_dbg: '文件 {file} 智能分段完成: {raw} 个原始段 -> {smart} 个智能段',
+    all_added_lines_ignored_dbg: '所有新增行都被代码内指令忽略: {file}',
+
+    // Reviewer (additional)
+    review_file_dbg: '审查文件: {file}',
+    review_file_progress: '[{index}/{total}] 审查: {file}（+{added} 行，{segments} 段）',
+    using_incremental_analyzer_progress: '使用增量式分析器进行分析...',
+    incremental_analyzer_failed_error: '增量式分析器失败: {error}',
+    ai_smart_analysis_start_progress: '开始AI智能分析，根据文件大小耗时不同，请耐心等待...',
+    smart_batching_process_error: 'AI智能批量分析过程出错: {error}',
+    fallback_simple_analysis_progress: '回退到简单分析方式...',
+    ai_analysis_start_batches: '开始AI分析，共{count}批文件',
+    batch_info_header: '批次 {index}/{total}: 分析{files}个文件',
+    batch_done_success: '批次 {index}/{total} 完成',
+    fallback_analysis_failed: '回退分析也失败: {error}',
+    serial_process_batches_info: '使用串行模式处理 {count} 个批次',
+    start_concurrency_enabled_info: '启用并发处理，并发数: {concurrency}',
+    start_concurrency_dbg: '使用并发模式处理 {count} 个批次',
+    serial_large_file_batch_info: '批次 {index}/{total}: 分析 {file} 文件，共{segments}段',
+    serial_small_file_batch_info: '批次 {index}/{total}: 分析 {files} 文件',
+    ai_analysis_done_summary: 'AI分析完成，发现{totalIssues}个问题，共耗时：{elapsed}秒',
+    rule_exec_failed_warn: '规则 {id} 执行失败: {error}',
+    skip_by_comments_dbg: '注释代码已跳过审查（{count}条匹配）',
+    skip_by_directives_dbg: '指令禁用范围已跳过审查（{count}条匹配）',
+    skip_ai_large_file: '跳过AI分析大文件: {file}',
+    blocking_risk_skip_all_ai_info: '本地规则存在阻断等级风险，跳过所有文件的AI分析。',
+    stream_read_large_file_dbg: '使用流式读取大文件: {file} ({sizeKB}KB)',
+    read_file_failed: '读取文件失败 {file}: {error}',
+
+    // Print Results
+    local_analysis_header: '本地规则审查结果',
+    ai_analysis_header: 'AI代码分析结果',
+    no_issues: '无',
+    file_label: '文件: {file}',
+    issue_label: '问题{index}:',
+    snippet_label: '代码片段：',
+    snippet_global_label: '代码片段：(全局性问题)',
+    risk_level_label: '风险等级：',
+    risk_reason_label: '风险原因：',
+    suggestions_label: '修改建议：',
+    tip_line_numbers: '提示：片段行号为源文件绝对行号，因清洗注释/无需审查片段可能出现跳跃，请忽略行号不连续。',
+    line_label: '行号：{line}',
+    line_range_label: '行号范围：{start}-{end}',
+
+    // AI Client
+    node_version_warn: '检测到 Node 版本 < 18 或缺少全局 fetch，可能导致连接异常。建议升级到 Node >=18。',
+    ai_batch_failed: 'AI批量文件分析失败: {error}',
+    ai_connection_failed: 'AI服务连接失败，终止分析过程',
+    ai_retry_warn: 'AI请求失败，重试（{attempt}/{retries}），等待{delay}ms: {error}',
+    read_ai_prompt_file_failed: '读取AI提示词文件失败 {file}: {error}',
+    read_custom_prompts_failed: '读取自定义提示词失败: {error}',
+    custom_prompts_label: '自定义提示词',
+    ignore_rule: '注意：代码可能经过预处理（剥离注释、跳过无需审查片段），因此行号前缀可能不连续。这是正常的，请严格忽略“行号跳跃/行号不连续/被预处理移除”等现象，不要将其视为问题或风险，也不要提出“检查代码完整性/补全缺失代码”类建议。仅针对给定片段中的有效代码提出问题与修改建议。',
+    // Batch and files intro/instruction
+    batch_intro: '我会发送一个批次的文件进行代码审查。其中可能包含分段文件（大文件被分成多段）。对于分段文件，请在收到所有段后进行整体分析。每个问题用空行分隔，务必包含“文件路径：绝对路径”与代码片段，且禁止任何“第X行/第X-Y行”等行号或行范围描述。',
+    batch_files_intro: '我会一次性发送多个文件的完整代码，请逐文件进行审查并返回结果。每个问题用空行分隔，务必包含“文件路径：绝对路径”与代码片段，且禁止任何“第X行/第X-Y行”等行号或行范围描述。',
+    final_instruction_batch: '请逐文件进行审查，每个问题用空行分隔，必须包含“文件路径：绝对路径”和具体的代码片段。禁止使用文字行号或行范围描述（如“第X行/第X-Y行”）；如片段中存在每行的[n]前缀请原样保留。',
+    file_failed_static_suffix: '（本地审查未通过）',
+    // Local rule hints
+    local_rule_findings: '本地规则发现的问题',
+    local_rule_findings_header: '[本地规则发现的问题 - {file}]',
+    inline_suggestion: '；建议：{suggestion}',
+    local_rule_hint_line: '{index}. 片段（{risk}）：{message}{suggest}；代码片段：{snippet}',
+    // Diff prompts and logs
+    ai_diff_start_dbg: '开始Git Diff分析: {file}（{added} 行新增代码）',
+    ai_diff_send_dbg: '发送Git Diff AI请求 - 模型: {model}，消息数: {messages}',
+    ai_diff_done_dbg: 'Git Diff分析完成: {file}，发现 {issues} 个问题',
+    ai_issues_found_n_dbg: 'AI分析发现 {count} 个问题',
+    diff_intro: '请对以下Git变更进行代码审查。重点关注新增的代码行（+号标记），上下文代码仅供理解，无需审查。',
+    diff_added_lines_label: '新增代码行数：',
+    diff_smart_segments_label: '智能分段数：',
+    diff_changes_label: '变更内容：',
+    diff_segment_title: '智能分段 {index}/{total}',
+    diff_segment_meta: '行范围: {start}-{end}, 新增{added}行, 约{tokens} tokens',
+    diff_final_instruction: '请仅对标记为“+”的新增代码行进行审查，忽略删除行（-）和上下文行。每个问题用空行分隔，必须包含“文件路径：{file}”和具体的代码片段。禁止使用文字行号或行范围描述（如“第X行/第X-Y行”）；如片段中存在每行的[行号]前缀请原样保留。',
+    // Fallback messages for static/local rules
+    fallback_static_reason: '基于本地规则：{message}',
+    fallback_static_suggestion: '请根据本地规则进行复核与修复，并补充测试与监控以验证风险。',
+
+    // Pool
+    init_pool_dbg: '初始化AI客户端池，大小: {size}',
+    pool_init_done_dbg: 'AI客户端池初始化完成，共{count}个客户端',
+    start_concurrent_dbg: '开始并发处理 {count} 个批次',
+    concurrent_done_dbg: '并发处理完成: 成功 {succ}, 失败 {fail}',
+    concurrent_group_failed: '文件组 {index} 处理失败: {error}',
+    concurrent_processing_error: '并发处理过程中发生错误: {error}',
+    cleanup_pool_dbg: '清理AI客户端池资源',
+    request_batch_start_dbg: '开始AI分析请求，批次 {index}，使用客户端: {client}',
+    seg_chunk_no_issues_dbg: '{file} 第 {chunk}/{total} 段未发现问题，AI响应内容: {preview}',
+    files_no_issues_dbg: '{files} 未发现问题，AI响应内容: {preview}',
+    issues_risk_levels_dbg: '{file} 发现的问题风险等级: {levels}',
+    issues_details_dbg: '{file} 发现的问题详情:',
+    issue_item_dbg: '  问题 {index}: {risk} - {message}',
+    batch_start_regular: '开始批次 {i}/{total}：文件 {files}（{count} 个，tokens {tokens}）',
+    batch_start_segmented: '开始批次 {i}/{total}：分段文件 {path}，总段数 {segments}',
+    batch_complete: '批次 {i}/{total} 完成：{context}，发现 {issues} 个问题，用时 {secs}s',
+    batch_process_failed: '批次 {i} 处理失败：{error}',
+    batch_retry_warn: '批次 {i} 请求失败，进行第 {retry} 次重试: {error}',
+    batch_retry_error: '批次 {i} 多次重试仍失败（{max} 次）: {error}',
+
+    // Diff parser
+    git_diff_parse_failed: '获取git diff失败: {error}',
+    file_skipped_by_ignore_rule_dbg: '文件被忽略规则跳过: {file}',
+    smart_seg_done_dbg: '文件 {file} 智能分段完成: {orig} 个原始段 -> {smart} 个智能段',
+    rule_diff_exec_failed_warn: '规则 {id} 在diff模式下执行失败: {error}',
+    
+    // Segment analysis (large-file segmented processing)
+    segment_overall_start: '开始逐段分析文件: {file}，共 {total} 段{concurrency}{totalNote}',
+    segment_concurrency_note: '（并发 {workers}）',
+    segment_total_note: '（总段数 {totalChunks}，当前批次 {effectiveTotal}）',
+    segment_wait_start_dbg: '分段待启动：第 {index}/{total} 段 (行 {start}-{end})',
+    segment_worker_start_dbg: '启动分段并发协程 #{id}',
+    segment_schedule_dbg: '分段并发调度：workers={workers}, total={total}{note}',
+    segment_concurrency_done_dbg: '分段并发完成：已处理 {total}{extra} 段',
+    segment_start_label: '开始分析 {file} 第 {index}/{total} 段（行 {start}-{end}）',
+    segment_batch_prefix: '批次 {index}/{total} ',
+    segment_size_estimate_dbg: '预估 {tokens} tokens, 共 {lines} 行代码',
+    segment_prepare_content_dbg: '准备第 {index} 段代码内容...',
+    segment_build_prompt_dbg: '构建第 {index} 段分析提示词...',
+    segment_analysis_done_n_issues: '{batch}（{file}）第 {index} 段分析完成，发现 {count} 个问题',
+    segment_analysis_done_zero: '{batch}（{file}）第 {index} 段分析完成，发现 0 个问题',
+    segment_analysis_failed: '第 {index} 段分析失败: {error}',
+    segment_file_failed: '分段文件分析失败: {error}',
+    parse_seg_response_failed_warn: '解析AI响应失败: {error}',
+    parse_issue_section_failed_warn: '解析问题段落失败: {error}',
+    segment_prev_context_header: '**前面段落摘要**:',
+    segment_prev_context_item: '第{index}段(行{range}): {summary}',
+    segment_summary_marker: '**-----段落摘要-----**',
+    segment_response_parsed_info: '第 {index} 段响应解析完成，发现 {count} 个问题',
+    // Chunked response and request logs (AI client)
+    detected_segmented_batch_dbg: '检测到分段批次，改用分段整体分析：{path}（{segments}段）',
+    chunk_req_info_dbg: '发送分段AI请求 - 模型: {model}, 消息数: {count}',
+    chunk_req_preview_dbg: 'AI请求消息预览:\n{preview}',
+    chunk_req_preview_fail_dbg: 'AI请求消息预览失败: {error}',
+    preview_truncated_suffix: '...省略 {count} 字符',
+    ai_response_len_dbg: 'AI响应: {len} 字符',
+    chunk_continue_needed_dbg: '分段响应未完成，发送“继续”请求下一段',
+    chunk_continue_prompt: '继续',
+    segment_static_issues_header: '[本地规则发现的问题 - 第{index}段]',
+    segment_static_issue_line: '{index}. 片段（{risk}）：{message}{suggest}；{snippetLabel}{snippet}',
+    // File review status reasons
+    file_ext_not_supported_reason: '文件扩展名 {ext} 不在支持列表中',
+    file_reason_exact_match: '匹配精确模式',
+    file_reason_regex_match: '匹配正则表达式',
+    file_reason_glob_match: '匹配glob模式',
+    segment_prompt_template: '请对以下代码段进行完整的代码审查分析。这是一个大文件的第 {index}/{total} 段：\n\n{Lfile}{file}\n{Lcontent}\n```\n{content}\n```\n\n请仔细审查这段代码，查找以下类型的问题：\n- 类型安全问题（如使用any类型）\n- 安全漏洞\n- 性能问题\n- 代码质量问题\n- 最佳实践违反\n\n重要：请立即开始分析，不要只是确认收到。必须按以下格式输出每个发现的问题：\n\n**-----代码分析结果-----**\n{Lfile}{file}\n{Lsnippet}[具体的问题代码]\n{Lrisk}[高/中/低]\n{Lreason}[问题描述]\n{Lsuggestion}[具体的修改建议]\n\n如果发现多个问题，每个问题都要用 **-----代码分析结果-----** 开头。\n如果没有发现问题，请回复：\n\n**-----代码分析结果-----**\n本段代码无明显问题\n\n注意：如片段中每行包含形如 [n] 的源行号前缀，请在你的输出的代码片段中原样保留这些前缀，以便后续定位。\n\n分段上下文限制：不要评估“导入是否被使用”，严格忽略关于“未使用的导入/模块/依赖”的任何提示或建议（包括建议删除未使用的导入）。',
+    // Static rule i18n (Best Practices)
+    rule_BP001_name: '调试代码',
+    rule_BP001_message: '发现调试代码，建议在提交前移除',
+    rule_BP001_suggestion: '使用日志系统替代console.log',
+    rule_BP002_name: '魔法数字',
+    rule_BP002_message: '检测到魔法数字，建议使用常量定义',
+    rule_BP002_suggestion: '将数字定义为有意义的常量',
+    rule_BP003_name: '空的异常捕获块',
+    rule_BP003_message: '检测到空的catch块，可能隐藏错误并导致不可预期行为',
+    rule_BP003_suggestion: '记录日志或采取补救措施，避免吞掉异常',
+    rule_BP004_name: '忽略TypeScript类型检查',
+    rule_BP004_message: '检测到@ts-ignore，可能掩盖类型错误',
+    rule_BP004_suggestion: '修复类型问题或使用更精确的类型定义',
+    rule_BP005_name: '使用any类型',
+    rule_BP005_message: '检测到any类型，可能削弱类型系统保护',
+    rule_BP005_suggestion: '使用具体类型或泛型替代any，提高类型安全',
+    rule_BP006_name: '禁用ESLint规则',
+    rule_BP006_message: '检测到禁用ESLint，可能隐藏代码质量问题',
+    rule_BP006_suggestion: '只在必要范围局部禁用，并给出明确原因',
+    rule_BP007_name: '调试断点未移除',
+    rule_BP007_message: '检测到调试断点，可能影响线上行为',
+    rule_BP007_suggestion: '在提交前移除debugger并使用日志或断言',
+    rule_BP008_name: '过于宽泛的异常捕获',
+    rule_BP008_message: '捕获过于宽泛的异常类型且未进行适当处理',
+    rule_BP008_suggestion: '捕获具体的异常类型，并确保进行适当的日志记录或重新抛出',
+    rule_BP009_name: '打印堆栈而非日志记录',
+    rule_BP009_message: '检测到直接打印堆栈跟踪，可能导致信息丢失与不可控输出',
+    rule_BP009_suggestion: '使用结构化日志记录错误，并附带上下文信息',
+    rule_BP010_name: '进程级退出调用',
+    rule_BP010_message: '检测到System.exit，可能导致服务非预期中断',
+    rule_BP010_suggestion: '使用受控的停止流程（优雅关闭）、信号处理与资源回收',
+    rule_BP011_name: '使用root数据库用户',
+    rule_BP011_message: '检测到使用root作为数据库用户，存在安全与审计风险',
+    rule_BP011_suggestion: '使用最小权限的应用专用账户，分离权限与职责',
+    rule_BP012_name: '禁用CSRF（Spring Security）',
+    rule_BP012_message: '检测到全局禁用CSRF保护，可能导致跨站请求伪造风险',
+    rule_BP012_suggestion: '在必要的API上采用令牌/同源策略，避免全局关闭',
+    rule_BP013_name: '使用var声明',
+    rule_BP013_message: '检测到使用var声明变量，可能导致作用域问题',
+    rule_BP013_suggestion: '使用let或const替代var，提高代码安全性',
+
+    // Static rule i18n (Performance)
+    rule_PERF001_name: '循环内数据库查询',
+    rule_PERF001_message: '在循环内执行数据库查询，可能导致N+1查询问题',
+    rule_PERF001_suggestion: '使用批量查询或预加载数据',
+    rule_PERF002_name: '内存泄漏风险（定时器使用）',
+    rule_PERF002_message: '发现定时器使用，若未清理可能导致内存泄漏或残留任务',
+    rule_PERF002_suggestion: '确保在适当生命周期调用 clearInterval/clearTimeout 进行清理',
+    rule_PERF003_name: '同步文件IO阻塞',
+    rule_PERF003_message: '检测到同步文件IO，可能阻塞事件循环并影响吞吐',
+    rule_PERF003_suggestion: '优先使用异步IO或队列化处理，避免阻塞主线程',
+    rule_PERF004_name: '循环内网络请求',
+    rule_PERF004_message: '检测到循环内执行网络请求，可能导致级联延迟与拥塞',
+    rule_PERF004_suggestion: '合并请求、并发控制或批量处理，减少往返次数',
+    rule_PERF005_name: '循环内JSON序列化',
+    rule_PERF005_message: '循环内频繁序列化可能导致CPU开销过大',
+    rule_PERF005_suggestion: '将序列化移到循环外或进行缓存/批量处理',
+    rule_PERF006_name: '循环内正则编译',
+    rule_PERF006_message: '循环内重复编译正则会增加不必要的开销',
+    rule_PERF006_suggestion: '将正则常量化或预编译，避免在循环中创建',
+    rule_PERF007_name: '忙等待循环',
+    rule_PERF007_message: '检测到可能的忙等待循环，可能导致CPU飙升与资源浪费',
+    rule_PERF007_suggestion: '使用事件驱动或阻塞等待机制，避免空循环',
+    rule_PERF008_name: '循环内DOM布局抖动',
+    rule_PERF008_message: '循环内读取布局信息会触发频繁回流/重绘',
+    rule_PERF008_suggestion: '合并DOM读写、使用批处理、减少同步布局查询',
+    rule_PERF009_name: '阻塞等待（sleep）',
+    rule_PERF009_message: '检测到阻塞等待调用，可能降低服务吞吐和响应',
+    rule_PERF009_suggestion: '改用异步等待或限流/队列机制，避免阻塞主线程',
+    rule_PERF010_name: '无界线程池',
+    rule_PERF010_message: '检测到无界线程池，可能导致线程爆炸与资源枯竭',
+    rule_PERF010_suggestion: '使用有界线程池并设置合理最大值与队列长度',
+    rule_PERF011_name: '循环内字符串拼接',
+    rule_PERF011_message: '循环内频繁字符串拼接会造成较大CPU与内存开销',
+    rule_PERF011_suggestion: '使用StringBuilder/列表收集再join，或其他批量化策略',
+    rule_PERF012_name: '循环内创建数据库连接',
+    rule_PERF012_message: '循环内反复创建数据库连接会导致严重性能问题',
+    rule_PERF012_suggestion: '使用连接池与复用策略，在循环外预先获取连接',
+    rule_PERF013_name: 'HTTP请求缺少超时（Python）',
+    rule_PERF013_message: '网络请求未设置超时会造成资源悬挂与吞吐下降',
+    rule_PERF013_suggestion: '设置合理的timeout参数，并对重试与熔断进行控制',
+
+    // Static rule i18n (Security)
+    rule_SEC001_name: '硬编码密码检测',
+    rule_SEC001_message: '发现硬编码的密码或密钥',
+    rule_SEC001_suggestion: '使用环境变量或安全的密钥管理服务',
+    rule_SEC002_name: 'SQL注入风险',
+    rule_SEC002_message: '发现字符串拼接SQL查询，存在SQL注入风险',
+    rule_SEC002_suggestion: '使用参数化查询或ORM的安全方法',
+    rule_SEC003_name: 'XSS风险',
+    rule_SEC003_message: '发现直接操作HTML内容，可能存在XSS风险',
+    rule_SEC003_suggestion: '使用textContent或安全的DOM操作方法',
+    rule_SEC004_name: '命令注入风险',
+    rule_SEC004_message: '发现命令执行函数调用，且可能包含用户输入',
+    rule_SEC004_suggestion: '避免使用用户输入构造命令，或进行严格的输入验证',
+    rule_SEC005_name: '路径遍历风险',
+    rule_SEC005_message: '可能存在路径遍历或未校验的文件路径使用',
+    rule_SEC005_suggestion: '对路径进行规范化、白名单校验，并避免直接拼接用户输入',
+    rule_SEC006_name: '禁用SSL证书校验',
+    rule_SEC006_message: '发现禁用SSL证书校验的HTTP请求',
+    rule_SEC006_suggestion: '启用证书校验或使用可信证书，避免中间人攻击',
+    rule_SEC007_name: '弱加密算法使用',
+    rule_SEC007_message: '检测到MD5/SHA1等弱加密算法的使用',
+    rule_SEC007_suggestion: '使用更安全的算法，如SHA-256/512、Argon2、bcrypt、scrypt',
+    rule_SEC008_name: '硬编码密钥/Token',
+    rule_SEC008_message: '检测到硬编码的密钥或访问令牌',
+    rule_SEC008_suggestion: '将敏感信息存放在安全的密钥管理或环境变量中',
+    rule_SEC009_name: '不安全反序列化',
+    rule_SEC009_message: '检测到潜在的不安全反序列化操作',
+    rule_SEC009_suggestion: '使用安全的反序列化方式，例如 yaml.safe_load，避免反序列化不可信数据',
+    rule_SEC010_name: 'SSRF风险',
+    rule_SEC010_message: '检测到可能由用户输入构成的URL请求，存在SSRF风险',
+    rule_SEC010_suggestion: '对外部URL进行白名单限制并校验，禁止访问内部地址',
+    rule_SEC011_name: 'NoSQL注入风险',
+    rule_SEC011_message: '检测到可能的NoSQL注入（动态拼接查询条件）',
+    rule_SEC011_suggestion: '使用参数化查询或安全的查询构建器，避免直接拼接',
+    rule_SEC012_name: '开放重定向',
+    rule_SEC012_message: '检测到基于用户输入的重定向，可能导致开放重定向',
+    rule_SEC012_suggestion: '对目标URL进行白名单校验或固定化处理',
+    rule_SEC013_name: '系统命令执行（Python）',
+    rule_SEC013_message: '检测到系统命令执行调用，若包含用户输入可能导致命令注入',
+    rule_SEC013_suggestion: '避免直接调用系统命令，改用安全库或严格白名单参数',
+    rule_SEC014_name: '不安全随机数',
+    rule_SEC014_message: '检测到在安全相关场景中使用非加密安全的随机数生成方法',
+    rule_SEC014_suggestion: '使用加密安全的随机数生成器，如 crypto.randomBytes、secrets.SystemRandom',
+    rule_SEC015_name: '危险的eval/Function使用',
+    rule_SEC015_message: '检测到可能导致代码注入的动态执行',
+    rule_SEC015_suggestion: '避免使用eval/Function，改用安全的解析与映射逻辑',
+    rule_SEC016_name: '原型污染',
+    rule_SEC016_message: '检测到对对象原型的直接赋值，可能导致原型污染',
+    rule_SEC016_suggestion: '避免从不可信数据合并到对象原型，使用安全的合并策略',
+    rule_SEC017_name: 'Java字符串拼接SQL执行',
+    rule_SEC017_message: '检测到通过字符串拼接构造SQL语句的执行',
+    rule_SEC017_suggestion: '使用PreparedStatement与占位符进行参数化查询',
+    rule_SEC018_name: 'jQuery.html导致XSS风险',
+    rule_SEC018_message: '检测到直接注入HTML内容，可能导致XSS',
+    rule_SEC018_suggestion: '使用text()或可信模板引擎进行转义输出',
+    rule_SEC019_name: '过大文件权限（777）',
+    rule_SEC019_message: '检测到设置过大的文件权限，存在安全风险',
+    rule_SEC019_suggestion: '使用最小权限原则，避免设置777等过宽权限',
+    rule_SEC020_name: '系统命令执行（多语言）',
+    rule_SEC020_message: '检测到系统命令执行调用，若包含用户输入可能导致命令注入',
+    rule_SEC020_suggestion: '避免直接调用系统命令，改用安全库或严格白名单参数',
+    rule_SEC021_name: '禁用TLS校验（Node）',
+    rule_SEC021_message: '检测到禁用TLS证书校验的配置',
+    rule_SEC021_suggestion: '启用证书校验并使用可信CA，避免中间人攻击',
+    rule_SEC022_name: 'CORS任意来源',
+    rule_SEC022_message: '检测到CORS允许任意来源，可能导致跨域数据泄露',
+    rule_SEC022_suggestion: '仅对可信来源开放，或使用令牌校验与细粒度策略',
+    rule_SEC023_name: 'LDAP注入风险',
+    rule_SEC023_message: '检测到基于字符串拼接的LDAP查询过滤器',
+    rule_SEC023_suggestion: '使用安全的过滤器构造与参数绑定，避免直接拼接',
+    rule_SEC024_name: 'XXE（XML外部实体）风险',
+    rule_SEC024_message: '检测到可能的XML解析，未禁用外部实体可能导致XXE',
+    rule_SEC024_suggestion: '禁用外部实体解析，或使用安全解析库（如defusedxml）',
+    rule_SEC025_name: 'Java HostnameVerifier始终返回true',
+    rule_SEC025_message: '检测到跳过主机名校验的HTTPS验证',
+    rule_SEC025_suggestion: '实现严格的主机名校验逻辑，避免任意通过',
+    rule_SEC026_name: 'Node禁用证书错误忽略',
+    rule_SEC026_message: '检测到全局禁用证书错误的环境变量设置',
+    rule_SEC026_suggestion: '移除该设置并使用合法证书，或在测试环境隔离',
+    rule_SEC027_name: '连接字符串包含凭据',
+    rule_SEC027_message: '检测到在连接字符串中硬编码了账号密码',
+    rule_SEC027_suggestion: '使用环境变量或安全凭据存储，避免明文出现在代码中',
+    rule_SEC028_name: '日志输出敏感信息',
+    rule_SEC028_message: '检测到将敏感信息输出到日志',
+    rule_SEC028_suggestion: '对敏感字段进行脱敏或完全避免记录',
+    rule_SEC029_name: 'Mass Assignment（Rails/Laravel）',
+    rule_SEC029_message: '检测到可能的批量赋值风险，未进行字段白名单校验',
+    rule_SEC029_suggestion: '启用强参数/属性白名单，仅允许安全字段写入',
+    rule_SEC030_name: '禁用TLS校验（Go）',
+    rule_SEC030_message: '检测到在Go中禁用了TLS证书校验',
+    rule_SEC030_suggestion: '启用证书校验并使用可信CA，避免中间人攻击',
+    rule_SEC031_name: '禁用证书校验（C#）',
+    rule_SEC031_message: '检测到覆盖全局证书校验回调，可能接受任意证书',
+    rule_SEC031_suggestion: '移除该回调并使用正确的证书验证机制',
+    rule_SEC032_name: 'Entity Framework原生SQL拼接',
+    rule_SEC032_message: '检测到EF Core使用FromSqlRaw并进行字符串拼接',
+    rule_SEC032_suggestion: '使用FromSqlInterpolated或参数化查询，避免注入风险',
+    rule_SEC033_name: 'Go系统命令执行',
+    rule_SEC033_message: '检测到Go中执行系统命令，若包含用户输入可能导致命令注入',
+    rule_SEC033_suggestion: '避免使用shell -c与拼接命令，采用白名单参数与直接可执行路径',
+    rule_SEC034_name: '不安全随机数（Go）',
+    rule_SEC034_message: '检测到使用math/rand生成随机数，非加密安全',
+    rule_SEC034_suggestion: '使用crypto/rand或安全随机数库生成敏感令牌与密钥',
+  },
+  'en-US': {
+    // Git hook script messages (pre-rendered at install time)
+    hook_header_comment: 'Smart Code Review - pre-commit hook (multi-project compatible; locates CLI via staged paths)',
+    hook_start_review: '🔍 Starting code review...',
+    hook_no_staged: '📭 No staged files to review',
+    hook_found_staged_header: '📁 Found staged files:',
+    hook_cd_repo_fail: '❌ Failed to cd to repo root',
+    hook_cmd_not_found1: '❌ smart-review not found. Please install in the subproject: npm i -D smart-review',
+    hook_cmd_not_found2: '   Or install at repo root for unified use: npm i -D smart-review',
+    hook_use_command_prefix: '⚙️  Using command:',
+    hook_review_fail: '❌ Code review failed; please fix issues and retry commit',
+    hook_review_pass: '✅ Code review passed; continuing commit',
+
+    // Install
+    install_search_git_root_dbg: 'Searching for Git root, starting from {dir}...',
+    install_found_git_root_success: 'Found Git root: {dir}',
+    install_no_git_use_current: 'ℹ️  .git directory not found, using current directory as project root',
+    install_start: '🚀 Starting installation of Smart Code Review system...',
+    install_done_success: '🎉 Smart Code Review system installed successfully!',
+    install_bundled_info: '💡 Default config and rules are bundled; works out-of-the-box',
+    install_customize_tip: '📝 To customize, edit config files under .smart-review/',
+    install_failed: 'Installation failed: {error}',
+    install_create_review_dir: 'Created .smart-review directory',
+    install_create_ai_rules_dir: 'Created ai-rules subdirectory (AI prompts)',
+    install_create_local_rules_dir: 'Created local-rules subdirectory (static rules)',
+    install_create_template_success: 'Created {desc}',
+    install_git_missing: 'Git not detected. Please install and retry: {url}',
+    install_init_git_warn: 'No .git directory detected. Attempting to initialize a Git repository...',
+    install_init_git_failed: 'Failed to initialize Git repository; skipping hook installation',
+    install_precommit_installed_success: 'Installed pre-commit Git hook',
+    install_precommit_perm_warn: 'Cannot set executable permission, but hook file created',
+    install_test_hook: '🧪 Testing Git hook...',
+    install_test_hook_success: 'Git hook check passed',
+    install_hook_missing: 'Hook file does not exist',
+    install_hook_perm_dbg: 'Hook file mode: {mode}, executable: {exec}',
+    install_hook_perm_fix_warn: 'Hook file not executable; trying to reset permission...',
+    install_hook_perm_check_failed: 'Failed to check hook permissions: {error}',
+    install_optional_header: '📝 Optional Configuration:',
+    install_optional_item1: '1. Edit .smart-review/smart-review.json to configure AI and risk levels',
+    install_optional_item2: '2. Add static rule files under .smart-review/local-rules/',
+    install_optional_item3: '3. Add AI prompt files under .smart-review/ai-rules/',
+    install_optional_item4: '4. Set OPENAI_API_KEY environment variable to enable AI review',
+    install_paths_header: '⚙️  Config Paths:',
+    install_local_rules_path: 'Static rules: {path}',
+    install_ai_rules_path: 'AI prompts: {path}',
+    install_test_header: '🔧 Test Commands:',
+    install_test_git_commit: 'git add . && git commit -m "test"  # Test commit to trigger review',
+    install_test_cli: 'npx smart-review --files test/src/test-file.js  # Manual review test (project CLI)',
+    // System prompt templates
+    system_prompt_template: 'You are a senior code review and optimization expert.\n\nStrictly follow this output format per issue, wrapped by start/end markers and separated by a blank line:\n{start}\n{Lfile}{absolute file path}\n{Lsnippet}{specific code snippet; if each line has a [n] prefix, keep it}\n{Lrisk}{Critical/High/Medium/Low/Suggestion}\n{Lreason}{detailed reason}\n{Lsuggestion}{specific, actionable modifications}\n{end}\n\nRules:\n- Always include the absolute file path and a concrete code snippet; do not use textual line numbers or ranges (e.g., "line X" or "lines X-Y").\n- If snippet lines include [n] prefixes, keep them exactly.\n- Because of pre-processing (comments stripped, ignored sections), line numbers can be non-contiguous. This is normal; ignore such gaps and NEVER treat them as an issue.\n- Focus on Security, Performance, Code Quality, Design & Architecture.',
+    diff_system_prompt_template: 'You review incremental Git changes.\n\nOnly review added lines marked by "+". Deleted "-" and context lines are for understanding only.\n\nOutput format per issue with start/end markers and blank line separation:\n{start}\n{Lfile}{absolute file path}\n{Lsnippet}{added code snippet only; if lines have [n] prefixes, keep them}\n{Lrisk}{Critical/High/Medium/Low/Suggestion}\n{Lreason}{why added code introduces issues}\n{Lsuggestion}{specific, actionable modifications}\n{end}\n\nImportant:\n- Snippet must only contain newly added code (without the "+" prefix), but keep any [n] line number prefixes.\n- Ignore non-contiguous line numbers caused by pre-processing or partial diffs.',
+    // CLI
+    cli_start: 'Code review starting, please wait...',
+    debug_enabled: 'Debug log mode enabled via CLI argument',
+    ai_disabled: 'AI analysis disabled via CLI argument',
+    ai_enabled: 'AI analysis enabled via CLI argument',
+    diff_only_enabled: 'Git Diff incremental review mode enabled',
+    usage_header: 'Usage:',
+    usage_staged: '  npx smart-code-reviewer --staged    # Review staged files',
+    usage_diffonly: '  npx smart-code-reviewer --staged --diff-only  # Review only changes (git diff)',
+    usage_files: '  npx smart-code-reviewer --files file1,file2  # Review specific files',
+    review_error: 'Review failed: {error}',
+
+    // Config loader
+    external_config_parse_failed_warn: 'External config parse failed; using default: {error}',
+    use_external_rules_only_info: 'Using external rules only: loading rules from local-rules directory',
+    load_external_rules_failed_warn: 'Failed to load external rules: {error}',
+    temp_file_method_failed_fallback_info: 'Temp-file approach failed; falling back to base64: {error}',
+    load_rule_file_failed_warn: 'Failed to load rule file {file}: {error}',
+
+    // Reviewer
+    review_staged_start: 'Reviewing staged code...',
+    using_diff_mode: '🔍 Using Git Diff incremental review - only changed lines',
+    using_full_mode: '📁 Using full-file review mode',
+    no_staged_files: '📭 No staged files to review',
+    found_staged_files_n: '📁 Found {count} files to review',
+    get_staged_failed: 'Failed to get staged files: {error}',
+    review_specific_start: 'Reviewing specific files: {files}',
+    file_not_exists: 'File does not exist: {path}',
+    start_git_diff_mode: '🔍 Starting Git Diff incremental review...',
+    no_changes_skip: '📝 No changes in staged area, skipping review',
+    found_changed_files_n: '📊 Found {count} changed files, starting incremental review...',
+    // Merge/Rebase filters
+    merge_rebase_detected_info: '🔀 Git merge/rebase detected; filtering to conflict files',
+    merge_conflict_paths_found_n: '⚔️  Found {count} conflict file(s); reviewing only these',
+    merge_rebase_no_conflict_skip: '✅ No conflict files during merge/rebase; skipping review',
+    apply_static_rules_dbg: 'Applying static rule checks...',
+    static_rules_found_n_dbg: 'Static rules found {count} issues',
+    file_skipped_by_type: 'File skipped: {path} (ignored file type)',
+    blocking_risk_detected_skip_ai: 'Blocking risk detected ({levels}), skipping AI analysis',
+    blocking_risk_terminate: 'Blocking risk detected, terminating review',
+    ai_start_n_files: '🤖 Starting AI analysis for {count} files...',
+    ai_diff_failed: 'AI diff analysis failed for {path}: {error}',
+    git_diff_done: '✨ Git Diff incremental review completed',
+    git_diff_error: 'Git Diff review encountered an error: {error}',
+    smart_segmentation_done_dbg: 'Smart segmentation done for {file}: {raw} raw -> {smart} smart segments',
+    all_added_lines_ignored_dbg: 'All added lines ignored by inline directives: {file}',
+
+    // Reviewer (additional)
+    review_file_dbg: 'Reviewing file: {file}',
+    using_incremental_analyzer_progress: 'Using incremental analyzer...',
+    incremental_analyzer_failed_error: 'Incremental analyzer failed: {error}',
+    smart_batching_process_error: 'Smart batching process error: {error}',
+    ai_smart_analysis_start_progress: 'Starting AI analysis; time varies with file sizes...',
+    ai_analysis_start_batches: 'Starting AI analysis, total {count} batches',
+    batch_info_header: 'Batch {index}/{total}: analyzing {files} files',
+    batch_done_success: 'Batch {index}/{total} completed',
+    fallback_analysis_failed: 'Fallback analysis failed: {error}',
+    serial_process_batches_info: 'Processing {count} batches in serial mode',
+    serial_large_file_batch_info: 'Batch {index}/{total}: analyzing {file}, {segments} segments',
+    serial_small_file_batch_info: 'Batch {index}/{total}: analyzing {files}',
+    ai_analysis_done_summary: 'AI analysis done: {totalIssues} issues found, elapsed {elapsed}s',
+    rule_exec_failed_warn: 'Rule {id} execution failed: {error}',
+    skip_by_comments_dbg: 'Comments skipped from review ({count} matches)',
+    skip_by_directives_dbg: 'Directive-disabled ranges skipped ({count} matches)',
+    skip_ai_large_file: 'Skipping AI for large file: {file}',
+    blocking_risk_skip_all_ai_info: 'Blocking local risks present; skipping AI analysis for all files.',
+
+    // Print Results
+    local_analysis_header: 'Local Rule Analysis',
+    ai_analysis_header: 'AI Code Analysis',
+    no_issues: 'None',
+    file_label: 'File: {file}',
+    issue_label: 'Issue {index}:',
+    snippet_label: 'Code Snippet:',
+    snippet_global_label: 'Code Snippet: (Global issue)',
+    risk_level_label: 'Risk Level:',
+    risk_reason_label: 'Risk Reason:',
+    suggestions_label: 'Suggestions:',
+    tip_line_numbers: 'Note: Snippet line numbers are absolute source lines. Due to pre-processing (stripping comments/ignoring segments), lines may be non-contiguous — ignore such gaps.',
+    line_label: 'Line: {line}',
+    line_range_label: 'Line Range: {start}-{end}',
+
+    // AI Client
+    node_version_warn: 'Detected Node < 18 or missing global fetch, may cause connection issues. Please upgrade to Node >=18.',
+    ai_batch_failed: 'AI batch file analysis failed: {error}',
+    ai_connection_failed: 'AI service connection failed, terminating analysis',
+    ai_retry_warn: 'AI request failed, retry ({attempt}/{retries}), wait {delay}ms: {error}',
+    read_ai_prompt_file_failed: 'Failed to read AI prompt file {file}: {error}',
+    read_custom_prompts_failed: 'Failed to read custom AI prompts: {error}',
+    custom_prompts_label: 'Custom Prompts',
+    ignore_rule: 'Note: Code may be pre-processed (comments stripped, segments skipped), so line number prefixes can be non-contiguous. This is normal — strictly ignore "line jumps/non-contiguous/removed by pre-processing". Do not treat them as issues or risk reasons; do not suggest "check completeness/fill missing code". Only analyze the provided snippet.',
+    // Batch and files intro/instruction
+    batch_intro: 'I will send a batch of files for code review. Some may be segmented (large files split into chunks). For segmented files, analyze holistically after receiving all segments. Separate each issue with a blank line and include the absolute file path and a concrete code snippet. Do not use textual line numbers or ranges.',
+    batch_files_intro: 'I will send multiple complete files at once. Review per file and return issues. Separate issues with a blank line. Always include "File Path: absolute path" and a concrete code snippet. Do not use textual line numbers or ranges (e.g., "line X" or "lines X-Y").',
+    final_instruction_batch: 'Review each file. Separate each issue by a blank line, and include "File Path: absolute path" and a specific code snippet. Do not use textual line numbers or ranges (e.g., "line X" or "lines X-Y"). If snippet lines have [n] prefixes, keep them as-is.',
+    file_failed_static_suffix: ' (Local analysis failed)',
+    // Local rule hints
+    local_rule_findings: 'Local Rule Findings',
+    local_rule_findings_header: '[Local Rule Findings - {file}]',
+    inline_suggestion: '; Suggestion: {suggestion}',
+    local_rule_hint_line: '{index}. Snippet ({risk}): {message}{suggest}; Code: {snippet}',
+    // Diff prompts and logs
+    ai_diff_start_dbg: 'Starting Git Diff analysis: {file} ({added} added lines)',
+    ai_diff_send_dbg: 'Sending Git Diff AI request - model: {model}, messages: {messages}',
+    ai_diff_done_dbg: 'Git Diff analysis completed: {file}, found {issues} issues',
+    ai_issues_found_n_dbg: 'AI analysis found {count} issues',
+    diff_intro: 'Please review the following Git changes. Focus ONLY on added lines (+). Context lines are for understanding only.',
+    diff_added_lines_label: 'Added Lines: ',
+    diff_smart_segments_label: 'Smart Segments: ',
+    diff_changes_label: 'Changes:',
+    diff_segment_title: 'Smart Segment {index}/{total}',
+    diff_segment_meta: 'line range: {start}-{end}, added {added} lines, ~{tokens} tokens',
+    diff_final_instruction: 'Only review lines marked with "+" and ignore deletions ("-") and context. Separate each issue by a blank line and include "File Path: {file}" and a concrete code snippet. Do not use textual line numbers or ranges; keep [n] prefixes if present.',
+    // Fallback messages for static/local rules
+    fallback_static_reason: 'Based on local rules: {message}',
+    fallback_static_suggestion: 'Please review and fix per local rules, and add tests and monitoring to validate the risk.',
+    // Reviewer extra
+    review_file_progress: '[{index}/{total}] Reviewing: {file} (+{added} lines, {segments} segments)',
+    ai_file_progress_dbg: '🤖 [{index}/{total}] AI analysis: {file}',
+    incremental_analyzer_start: 'Using incremental analyzer...',
+    ai_start_progress_note: 'Starting AI analysis; duration varies by file size...',
+    fallback_simple_analysis_progress: 'Falling back to simple analysis...',
+    ai_start_batches_count_info: 'Starting AI analysis, {count} batches',
+    batch_start_regular_simple: 'Batch {i}/{total}: analyzing {count} files',
+    start_concurrency_enabled_info: 'Concurrency enabled, workers: {concurrency}',
+    start_serial_dbg: 'Using serial mode for {count} batches',
+    start_concurrency_dbg: 'Using concurrent mode for {count} batches',
+    review_file_path_dbg: 'Reviewing file: {path}',
+    review_file_failed: 'Reviewing file failed {file}: {error}',
+    skip_by_comments_dbg: 'Comments skipped from review ({count} matches)',
+    skip_by_directives_dbg: 'Directive-disabled ranges skipped ({count} matches)',
+    skip_ai_large_file: 'Skipping AI for large file: {file}',
+    incremental_analyzer_failed_error: 'Incremental analyzer failed: {error}',
+    fallback_analysis_failed: 'Fallback analysis failed: {error}',
+    stream_read_large_file_dbg: 'Streaming large file: {file} ({sizeKB}KB)',
+    read_file_failed: 'Failed to read file {file}: {error}',
+    blocking_risk_skip_all_ai_info: 'Blocking local risks present; skipping AI analysis for all files.',
+
+    // Pool
+    init_pool_dbg: 'Initializing AI client pool, size: {size}',
+    pool_init_done_dbg: 'AI client pool initialized, {count} clients',
+    start_concurrent_dbg: 'Starting concurrent processing for {count} batches',
+    concurrent_done_dbg: 'Concurrent processing finished: success {succ}, fail {fail}',
+    concurrent_group_failed: 'File group {index} failed: {error}',
+    concurrent_processing_error: 'Error during concurrent processing: {error}',
+    cleanup_pool_dbg: 'Cleaning AI client pool resources',
+    request_batch_start_dbg: 'Starting AI request, batch {index}, client: {client}',
+    seg_chunk_no_issues_dbg: '{file} chunk {chunk}/{total} no issues; AI response: {preview}',
+    files_no_issues_dbg: '{files} no issues; AI response: {preview}',
+    issues_risk_levels_dbg: '{file} issue risk levels: {levels}',
+    issues_details_dbg: '{file} issue details:',
+    issue_item_dbg: '  Issue {index}: {risk} - {message}',
+    batch_start_regular: 'Batch {i}/{total} start: files {files} ({count} files, tokens {tokens})',
+    batch_start_segmented: 'Batch {i}/{total} start: segmented file {path}, total segments {segments}',
+    batch_complete: 'Batch {i}/{total} done: {context}, {issues} issues, took {secs}s',
+    batch_process_failed: 'Batch {i} failed: {error}',
+    batch_retry_warn: 'Batch {i} failed, retry #{retry}: {error}',
+    batch_retry_error: 'Batch {i} failed after {max} retries: {error}',
+
+    // Diff parser
+    git_diff_parse_failed: 'Failed to get git diff: {error}',
+    file_skipped_by_ignore_rule_dbg: 'File skipped by ignore rules: {file}',
+    smart_seg_done_dbg: 'File {file} smart segmentation: {orig} original -> {smart} segments',
+    rule_diff_exec_failed_warn: 'Rule {id} failed in diff mode: {error}',
+    analyze_staged_changes_progress: 'Analyzing staged changes...',
+    all_added_lines_ignored_by_directives_dbg: 'All added lines ignored by in-code directives: {file}',
+    get_staged_file_failed_dbg: 'Failed to get staged file content {file}: {error}',
+    
+    // Segment analysis (large-file segmented processing)
+    segment_overall_start: 'Starting segmented analysis: {file}, total {total} segments{concurrency}{totalNote}',
+    segment_concurrency_note: ' (concurrency {workers})',
+    segment_total_note: ' (total segments {totalChunks}, current batch {effectiveTotal})',
+    segment_wait_start_dbg: 'Segment pending start: {index}/{total} (lines {start}-{end})',
+    segment_worker_start_dbg: 'Starting segment worker #{id}',
+    segment_schedule_dbg: 'Segment concurrency scheduling: workers={workers}, total={total}{note}',
+    segment_concurrency_done_dbg: 'Segment concurrency finished: processed {total}{extra} segments',
+    segment_start_label: 'Starting {file} segment {index}/{total} (lines {start}-{end})',
+    segment_batch_prefix: 'Batch {index}/{total} ',
+    segment_size_estimate_dbg: 'Estimated {tokens} tokens, {lines} lines of code',
+    segment_prepare_content_dbg: 'Preparing segment {index} code content...',
+    segment_build_prompt_dbg: 'Building prompt for segment {index}...',
+    segment_analysis_done_n_issues: '{batch}({file}) segment {index} analysis done; {count} issues found',
+    segment_analysis_done_zero: '{batch}({file}) segment {index} analysis done; 0 issues found',
+    segment_analysis_failed: 'Segment {index} analysis failed: {error}',
+    segment_file_failed: 'Segmented file analysis failed: {error}',
+    parse_seg_response_failed_warn: 'Failed to parse AI response: {error}',
+    parse_issue_section_failed_warn: 'Failed to parse issue section: {error}',
+    segment_prev_context_header: '**Previous Segment Summaries**:',
+    segment_prev_context_item: 'Segment {index} (lines {range}): {summary}',
+    segment_summary_marker: '**-----Segment Summary-----**',
+    segment_response_parsed_info: 'Segment {index} response parsed; {count} issues found',
+    // Chunked response and request logs (AI client)
+    detected_segmented_batch_dbg: 'Detected segmented batch; using overall analysis: {path} ({segments} segments)',
+    chunk_req_info_dbg: 'Send chunked AI request - model: {model}, messages: {count}',
+    chunk_req_preview_dbg: 'AI request messages preview:\n{preview}',
+    chunk_req_preview_fail_dbg: 'AI request preview failed: {error}',
+    preview_truncated_suffix: '...omitted {count} chars',
+    ai_response_len_dbg: 'AI response: {len} chars',
+    chunk_continue_needed_dbg: 'Chunked response incomplete; sending "continue" for next chunk',
+    chunk_continue_prompt: 'continue',
+    segment_static_issues_header: '[Local rule findings - Segment {index}]',
+    segment_static_issue_line: '{index}. Segment ({risk}): {message}{suggest}; {snippetLabel}{snippet}',
+    // File review status reasons
+    file_ext_not_supported_reason: 'File extension {ext} is not supported',
+    file_reason_exact_match: 'Exact match pattern',
+    file_reason_regex_match: 'Regex pattern matched',
+    file_reason_glob_match: 'Glob pattern matched',
+    segment_prompt_template: 'Please perform a thorough code review on the following code segment. This is segment {index}/{total} of a large file:\n\n{Lfile}{file}\n{Lcontent}\n```\n{content}\n```\n\nCarefully check for:\n- Type-safety issues (e.g., use of any)\n- Security vulnerabilities\n- Performance issues\n- Code quality problems\n- Violations of best practices\n\nImportant: Start analysis immediately; do not just acknowledge. You must output each finding in the following format:\n\n**-----Code Review Result-----**\n{Lfile}{file}\n{Lsnippet}[Specific problematic code]\n{Lrisk}[Critical/High/Medium/Low/Suggestion]\n{Lreason}[Problem description]\n{Lsuggestion}[Concrete suggestions]\n\nIf multiple issues are found, start every issue with **-----Code Review Result-----**.\nIf no issues are found, reply:\n\n**-----Code Review Result-----**\nNo obvious issues in this segment.\n\nNote: If each line contains a source-line prefix like [n], keep these prefixes unchanged in your output to help later localization.\n\nSegment context constraint: Do NOT evaluate whether imports/modules/dependencies are used in this segment; strictly ignore any suggestions about removing unused imports/modules/dependencies.',
+    // Static rule i18n (Best Practices)
+    rule_BP001_name: 'Debug code',
+    rule_BP001_message: 'Debug code found; remove before committing',
+    rule_BP001_suggestion: 'Use a logging system instead of console.log',
+    rule_BP002_name: 'Magic numbers',
+    rule_BP002_message: 'Magic numbers detected; define them as constants',
+    rule_BP002_suggestion: 'Define numbers as meaningful constants',
+    rule_BP003_name: 'Empty catch block',
+    rule_BP003_message: 'Empty catch may hide errors and cause unpredictable behavior',
+    rule_BP003_suggestion: 'Log or take remedial actions instead of swallowing exceptions',
+    rule_BP004_name: 'Ignore TypeScript type checking',
+    rule_BP004_message: 'Detected @ts-ignore; may conceal type errors',
+    rule_BP004_suggestion: 'Fix type issues or use precise type definitions',
+    rule_BP005_name: 'Use of any type',
+    rule_BP005_message: 'Using any weakens type safety guarantees',
+    rule_BP005_suggestion: 'Use concrete types or generics to improve safety',
+    rule_BP006_name: 'ESLint rule disabled',
+    rule_BP006_message: 'Disabling ESLint may hide code quality issues',
+    rule_BP006_suggestion: 'Disable locally only when necessary, and explain the reason',
+    rule_BP007_name: 'Debugger statement left',
+    rule_BP007_message: 'Debugger statement found; may affect production behavior',
+    rule_BP007_suggestion: 'Remove debugger before commit; use logs or assertions',
+    rule_BP008_name: 'Overly broad exception catch',
+    rule_BP008_message: 'Catching broad exception types without proper handling',
+    rule_BP008_suggestion: 'Catch specific types and ensure logging or rethrowing as needed',
+    rule_BP009_name: 'Print stack instead of logging',
+    rule_BP009_message: 'Direct stack printing may lose context and produce uncontrolled output',
+    rule_BP009_suggestion: 'Use structured logging with context information',
+    rule_BP010_name: 'Process-level exit call',
+    rule_BP010_message: 'System.exit detected; may cause unexpected service termination',
+    rule_BP010_suggestion: 'Use graceful shutdown, signal handling, and resource cleanup',
+    rule_BP011_name: 'Use root database user',
+    rule_BP011_message: 'Using root as DB user introduces security and audit risks',
+    rule_BP011_suggestion: 'Use a least-privileged application account and separate duties',
+    rule_BP012_name: 'Disable CSRF (Spring Security)',
+    rule_BP012_message: 'Globally disabling CSRF may cause CSRF vulnerabilities',
+    rule_BP012_suggestion: 'Use token/same-origin policies where needed; avoid global disable',
+    rule_BP013_name: 'Use of var declarations',
+    rule_BP013_message: 'Using var may cause scope issues',
+    rule_BP013_suggestion: 'Use let or const to improve safety',
+
+    // Static rule i18n (Performance)
+    rule_PERF001_name: 'Database queries inside loops',
+    rule_PERF001_message: 'Executing DB queries in loops may cause N+1 problems',
+    rule_PERF001_suggestion: 'Use batch queries or preload data',
+    rule_PERF002_name: 'Memory leak risk (timers)',
+    rule_PERF002_message: 'Timers without cleanup may cause leaks or lingering tasks',
+    rule_PERF002_suggestion: 'Call clearInterval/clearTimeout at the proper lifecycle point',
+    rule_PERF003_name: 'Synchronous file I/O blocking',
+    rule_PERF003_message: 'Sync file I/O may block the event loop and hurt throughput',
+    rule_PERF003_suggestion: 'Prefer async I/O or queued processing; avoid blocking the main thread',
+    rule_PERF004_name: 'Network requests inside loops',
+    rule_PERF004_message: 'Requests inside loops can cause cascading latency and congestion',
+    rule_PERF004_suggestion: 'Merge requests, control concurrency, or batch to reduce round-trips',
+    rule_PERF005_name: 'JSON serialization inside loops',
+    rule_PERF005_message: 'Frequent serialization in loops causes excessive CPU overhead',
+    rule_PERF005_suggestion: 'Move serialization out of the loop or cache/batch it',
+    rule_PERF006_name: 'Regex compilation inside loops',
+    rule_PERF006_message: 'Repeated regex compilation adds unnecessary overhead',
+    rule_PERF006_suggestion: 'Precompile or constantize regexes; avoid creating them in loops',
+    rule_PERF007_name: 'Busy-wait loops',
+    rule_PERF007_message: 'Possible busy-wait detected; can spike CPU and waste resources',
+    rule_PERF007_suggestion: 'Use event-driven or blocking waits; avoid empty loops',
+    rule_PERF008_name: 'Layout thrashing in loops',
+    rule_PERF008_message: 'Reading layout in loops triggers frequent reflow/repaint',
+    rule_PERF008_suggestion: 'Batch DOM reads/writes; reduce synchronous layout queries',
+    rule_PERF009_name: 'Blocking sleep',
+    rule_PERF009_message: 'Blocking waits reduce throughput and responsiveness',
+    rule_PERF009_suggestion: 'Use async waits or rate-limiting/queues; avoid blocking',
+    rule_PERF010_name: 'Unbounded thread pool',
+    rule_PERF010_message: 'Unbounded pools can explode thread count and exhaust resources',
+    rule_PERF010_suggestion: 'Use bounded pools with sane maximums and queue lengths',
+    rule_PERF011_name: 'String concatenation inside loops',
+    rule_PERF011_message: 'Frequent concatenation in loops consumes CPU and memory',
+    rule_PERF011_suggestion: 'Use StringBuilder/collect in lists then join, or batch strategies',
+    rule_PERF012_name: 'Create DB connections in loops',
+    rule_PERF012_message: 'Repeatedly creating DB connections causes severe performance issues',
+    rule_PERF012_suggestion: 'Use connection pools and reuse; acquire connections outside loops',
+    rule_PERF013_name: 'HTTP requests without timeout (Python)',
+    rule_PERF013_message: 'Requests without timeout can hang resources and reduce throughput',
+    rule_PERF013_suggestion: 'Set reasonable timeout; control retries and circuit breaking',
+
+    // Static rule i18n (Security)
+    rule_SEC001_name: 'Hard-coded password detection',
+    rule_SEC001_message: 'Hard-coded password or secret detected',
+    rule_SEC001_suggestion: 'Use environment variables or a secure secret manager',
+    rule_SEC002_name: 'SQL injection risk',
+    rule_SEC002_message: 'String-concatenated SQL detected; injection risk',
+    rule_SEC002_suggestion: 'Use parameterized queries or the ORM’s safe APIs',
+    rule_SEC003_name: 'XSS risk',
+    rule_SEC003_message: 'Direct HTML manipulation detected; possible XSS',
+    rule_SEC003_suggestion: 'Use textContent or safe DOM APIs',
+    rule_SEC004_name: 'Command injection risk',
+    rule_SEC004_message: 'Command execution with possible user input detected',
+    rule_SEC004_suggestion: 'Avoid constructing commands from user input; validate strictly',
+    rule_SEC005_name: 'Path traversal risk',
+    rule_SEC005_message: 'Potential path traversal or unvalidated file path usage',
+    rule_SEC005_suggestion: 'Normalize and whitelist paths; never concatenate untrusted input',
+    rule_SEC006_name: 'Disable SSL certificate verification',
+    rule_SEC006_message: 'HTTP request with certificate verification disabled detected',
+    rule_SEC006_suggestion: 'Enable verification and use trusted CAs; avoid MITM attacks',
+    rule_SEC007_name: 'Weak cryptographic algorithm',
+    rule_SEC007_message: 'Detected use of weak algorithms such as MD5/SHA-1',
+    rule_SEC007_suggestion: 'Use stronger algorithms: SHA-256/512, Argon2, bcrypt, scrypt',
+    rule_SEC008_name: 'Hard-coded secret/Token',
+    rule_SEC008_message: 'Hard-coded secret or access token detected',
+    rule_SEC008_suggestion: 'Store secrets in a manager or environment variables',
+    rule_SEC009_name: 'Unsafe deserialization',
+    rule_SEC009_message: 'Potentially unsafe deserialization detected',
+    rule_SEC009_suggestion: 'Use safe methods (e.g., yaml.safe_load); never deserialize untrusted data',
+    rule_SEC010_name: 'SSRF risk',
+    rule_SEC010_message: 'User-controlled URL request detected; SSRF risk',
+    rule_SEC010_suggestion: 'Whitelist external URLs; prohibit access to internal addresses',
+    rule_SEC011_name: 'NoSQL injection risk',
+    rule_SEC011_message: 'Possible NoSQL injection (dynamically concatenated conditions)',
+    rule_SEC011_suggestion: 'Use parameterized queries or safe builders; avoid concatenation',
+    rule_SEC012_name: 'Open redirect',
+    rule_SEC012_message: 'User-controlled redirection detected; open-redirect risk',
+    rule_SEC012_suggestion: 'Whitelist target URLs or fix them to safe destinations',
+    rule_SEC013_name: 'System command execution (Python)',
+    rule_SEC013_message: 'System command execution detected; injection risk if user input involved',
+    rule_SEC013_suggestion: 'Avoid direct system calls; use safe libraries or strict whitelists',
+    rule_SEC014_name: 'Insecure randomness',
+    rule_SEC014_message: 'Non-cryptographic RNG used in security-sensitive contexts',
+    rule_SEC014_suggestion: 'Use cryptographically secure RNGs (crypto.randomBytes, secrets.SystemRandom)',
+    rule_SEC015_name: 'Dangerous eval/Function usage',
+    rule_SEC015_message: 'Dynamic execution that may lead to code injection',
+    rule_SEC015_suggestion: 'Avoid eval/Function; use safe parsing/mapping logic',
+    rule_SEC016_name: 'Prototype pollution',
+    rule_SEC016_message: 'Direct assignment to object prototypes; may cause pollution',
+    rule_SEC016_suggestion: 'Avoid merging untrusted data into prototypes; use safe merging',
+    rule_SEC017_name: 'Java string-concatenated SQL execution',
+    rule_SEC017_message: 'SQL execution built via string concatenation detected',
+    rule_SEC017_suggestion: 'Use PreparedStatement with placeholders',
+    rule_SEC018_name: 'jQuery.html causing XSS risk',
+    rule_SEC018_message: 'Direct HTML injection detected; possible XSS',
+    rule_SEC018_suggestion: 'Use text() or trusted templating with escaping',
+    rule_SEC019_name: 'Overly permissive file mode (777)',
+    rule_SEC019_message: 'Setting wide-open file permissions detected',
+    rule_SEC019_suggestion: 'Apply least privilege; avoid 777 and similar modes',
+    rule_SEC020_name: 'System command execution (multi-language)',
+    rule_SEC020_message: 'System command execution detected; injection risk with user input',
+    rule_SEC020_suggestion: 'Avoid shell commands; use safe libraries and whitelist parameters',
+    rule_SEC021_name: 'Disable TLS verification (Node)',
+    rule_SEC021_message: 'TLS certificate verification disabled detected',
+    rule_SEC021_suggestion: 'Enable verification and use trusted CA to avoid MITM',
+    rule_SEC022_name: 'CORS allows any origin',
+    rule_SEC022_message: 'CORS allows "*"; may lead to cross-origin data leaks',
+    rule_SEC022_suggestion: 'Only allow trusted origins; use tokens and fine-grained policy',
+    rule_SEC023_name: 'LDAP injection risk',
+    rule_SEC023_message: 'String-concatenated LDAP filters detected',
+    rule_SEC023_suggestion: 'Build filters safely and bind parameters; avoid concatenation',
+    rule_SEC024_name: 'XXE (XML External Entity) risk',
+    rule_SEC024_message: 'XML parsing with external entities not disabled',
+    rule_SEC024_suggestion: 'Disable external entities or use safe libraries (e.g., defusedxml)',
+    rule_SEC025_name: 'Java HostnameVerifier always returns true',
+    rule_SEC025_message: 'Hostname verification bypass detected for HTTPS',
+    rule_SEC025_suggestion: 'Implement strict hostname verification to avoid permissive behavior',
+    rule_SEC026_name: 'Node ignore certificate errors',
+    rule_SEC026_message: 'Global env disables certificate errors detected',
+    rule_SEC026_suggestion: 'Remove the setting and use valid certs or isolate in test env',
+    rule_SEC027_name: 'Credentials in connection string',
+    rule_SEC027_message: 'Username/password hard-coded in connection string detected',
+    rule_SEC027_suggestion: 'Use env variables or secure credential storage; avoid plaintext in code',
+    rule_SEC028_name: 'Sensitive data in logs',
+    rule_SEC028_message: 'Sensitive information logged',
+    rule_SEC028_suggestion: 'Mask sensitive fields or avoid logging them altogether',
+    rule_SEC029_name: 'Mass Assignment (Rails/Laravel)',
+    rule_SEC029_message: 'Possible mass assignment risk; no whitelist validation',
+    rule_SEC029_suggestion: 'Enable strong parameters/whitelist; only allow safe fields',
+    rule_SEC030_name: 'Disable TLS verification (Go)',
+    rule_SEC030_message: 'TLS certificate verification disabled in Go detected',
+    rule_SEC030_suggestion: 'Enable verification and use trusted CA; avoid MITM attacks',
+    rule_SEC031_name: 'Disable certificate validation (C#)',
+    rule_SEC031_message: 'Overriding global certificate validation; may accept any certificate',
+    rule_SEC031_suggestion: 'Remove the override and use proper validation mechanisms',
+    rule_SEC032_name: 'EF Core raw SQL concatenation',
+    rule_SEC032_message: 'Using FromSqlRaw with string concatenation detected',
+    rule_SEC032_suggestion: 'Use FromSqlInterpolated or parameterized queries to avoid injection',
+    rule_SEC033_name: 'Go system command execution',
+    rule_SEC033_message: 'System command execution in Go; injection risk if user input involved',
+    rule_SEC033_suggestion: 'Avoid shell -c and concatenation; whitelist parameters and exec paths',
+    rule_SEC034_name: 'Insecure randomness (Go)',
+    rule_SEC034_message: 'Using math/rand for randomness; not cryptographically secure',
+    rule_SEC034_suggestion: 'Use crypto/rand or secure RNG libraries for tokens and keys',
+  }
+};
+
+export function t(configOrLocale, key, params) {
+  const loc = getLocale(configOrLocale);
+  const dict = MESSAGES[loc] || MESSAGES['zh-CN'];
+  const msg = dict[key] || key;
+  return format(msg, params);
+}
+
+// Prompt builders for system and diff prompts in both languages.
+export function buildPrompts(localeOrConfig) {
+  const loc = getLocale(localeOrConfig);
+  const L = FIELD_LABELS[loc] || FIELD_LABELS['zh-CN'];
+  // Shared analysis markers for parser compatibility (locale-driven, no hardcoded branching)
+  const MARKERS = {
+    'zh-CN': {
+      start: '**-----代码分析结果开始-----**',
+      end: '**-----代码分析结果结束-----**',
+      startDiff: '**-----Git Diff代码分析结果开始-----**',
+      endDiff: '**-----Git Diff代码分析结果结束-----**'
+    },
+    'en-US': {
+      start: '**-----Code Analysis Result Start-----**',
+      end: '**-----Code Analysis Result End-----**',
+      startDiff: '**-----Git Diff Code Analysis Result Start-----**',
+      endDiff: '**-----Git Diff Code Analysis Result End-----**'
+    }
+  };
+  const m = MARKERS[loc] || MARKERS['en-US'];
+
+  const systemPrompt = t(loc, 'system_prompt_template', {
+    start: m.start,
+    end: m.end,
+    Lfile: L.file,
+    Lsnippet: L.snippet,
+    Lrisk: L.risk,
+    Lreason: L.reason,
+    Lsuggestion: L.suggestion
+  });
+
+  const diffSystemPrompt = t(loc, 'diff_system_prompt_template', {
+    start: m.startDiff,
+    end: m.endDiff,
+    Lfile: L.file,
+    Lsnippet: L.snippet,
+    Lrisk: L.risk,
+    Lreason: L.reason,
+    Lsuggestion: L.suggestion
+  });
+
+  return { systemPrompt, diffSystemPrompt };
+}