@yeepay/coderocket-mcp 1.2.4 → 1.2.6

package/dist/toolDefinitions.js

@@ -0,0 +1,141 @@
+import { z } from 'zod';
+import { ReviewCodeRequestSchema, ReviewChangesRequestSchema, ReviewCommitRequestSchema, ReviewFilesRequestSchema, ConfigureAIServiceRequestSchema, } from './types.js';
+export const toolDefinitions = [
+    {
+        name: 'review_code',
+        description: `🔍 **代码片段智能审查工具**
+
+**功能**: 对提供的代码片段进行深度质量分析，提供专业的改进建议和最佳实践指导。
+
+**适用场景**:
+- 代码重构前的质量评估
+- 新功能开发的代码审查
+- 学习和改进编程技能
+- 代码规范性检查
+
+**AI分析维度**:
+- 代码逻辑和算法效率
+- 安全漏洞和潜在风险
+- 可读性和维护性
+- 性能优化建议
+- 最佳实践合规性
+
+**输出格式**: 结构化的审查报告，包含状态评级、摘要和详细分析`,
+        schema: ReviewCodeRequestSchema,
+    },
+    {
+        name: 'review_changes',
+        description: `🚀 **Git变更自动审查工具**
+
+**功能**: 自动检测并审查当前Git仓库中所有未提交的代码变更，无需手动传递代码内容。
+
+**适用场景**:
+- 提交前的自动化代码质量检查
+- 开发过程中的实时代码审查
+- CI/CD流程中的质量门禁
+- 团队协作中的代码规范检查
+
+**AI分析维度**:
+- 变更逻辑的合理性和完整性
+- 代码质量和最佳实践遵循
+- 潜在的安全风险和性能问题
+- 与现有代码的一致性检查
+- 测试覆盖和文档更新建议
+
+**自动化特性**:
+- 零参数调用，自动检测Git变更
+- 支持已暂存和未暂存变更的分别审查
+- 智能识别文件类型和编程语言
+- 提供上下文相关的改进建议
+
+**输出格式**: 详细的变更审查报告，包含文件级和整体级分析`,
+        schema: ReviewChangesRequestSchema,
+    },
+    {
+        name: 'review_commit',
+        description: `📝 **Git提交智能审查工具**
+
+**功能**: 分析Git提交的代码变更，评估变更的质量、影响范围和潜在风险。
+
+**适用场景**:
+- 代码合并前的质量把关
+- 提交历史的质量回顾
+- 团队代码审查流程
+- 持续集成质量检查
+
+**AI分析维度**:
+- 变更逻辑的合理性
+- 代码风格一致性
+- 潜在的破坏性变更
+- 测试覆盖率影响
+- 文档更新需求
+
+**输出格式**: 详细的提交审查报告，包含变更摘要和风险评估`,
+        schema: ReviewCommitRequestSchema,
+    },
+    {
+        name: 'review_files',
+        description: `📁 **多文件批量审查工具**
+
+**功能**: 对指定的多个文件进行批量代码质量审查，提供整体项目质量评估。
+
+**适用场景**:
+- 项目整体质量评估
+- 重构前的现状分析
+- 新团队成员代码熟悉
+- 技术债务识别
+
+**AI分析维度**:
+- 文件间依赖关系分析
+- 架构设计合理性
+- 代码重复度检测
+- 模块化程度评估
+- 整体代码健康度
+
+**输出格式**: 综合性的多文件审查报告，包含文件级和项目级分析`,
+        schema: ReviewFilesRequestSchema,
+    },
+    {
+        name: 'configure_ai_service',
+        description: `⚙️ **AI服务配置管理工具**
+
+**功能**: 配置和管理CodeRocket使用的AI服务，包括API密钥设置、服务选择和参数调优。
+
+**支持的AI服务**:
+- **Gemini**: Google的先进AI模型，擅长代码分析和建议
+- **ClaudeCode**: Anthropic的专业代码审查模型
+
+**配置选项**:
+- API密钥管理（项目级/全局级）
+- 服务优先级设置
+- 超时和重试参数
+- 自动故障转移配置
+
+**安全性**: API密钥加密存储，支持环境变量配置
+
+**输出格式**: 配置操作结果和当前配置状态`,
+        schema: ConfigureAIServiceRequestSchema,
+    },
+    {
+        name: 'get_ai_service_status',
+        description: `📊 **AI服务状态监控工具**
+
+**功能**: 获取所有已配置AI服务的实时状态信息，包括可用性、配置状态和性能指标。
+
+**监控信息**:
+- 服务连接状态
+- API配额使用情况
+- 响应时间统计
+- 错误率监控
+- 配置完整性检查
+
+**故障诊断**:
+- 自动检测配置问题
+- 提供修复建议
+- 显示详细错误信息
+
+**输出格式**: 完整的服务状态报告，包含所有服务的健康状况`,
+        schema: z.object({}), // 无参数工具
+    },
+];
+//# sourceMappingURL=toolDefinitions.js.map

package/dist/toolDefinitions.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"toolDefinitions.js","sourceRoot":"","sources":["../src/toolDefinitions.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EACL,uBAAuB,EACvB,0BAA0B,EAC1B,yBAAyB,EACzB,wBAAwB,EACxB,+BAA+B,GAChC,MAAM,YAAY,CAAC;AAQpB,MAAM,CAAC,MAAM,eAAe,GAAc;IACxC;QACE,IAAI,EAAE,aAAa;QACnB,WAAW,EAAE;;;;;;;;;;;;;;;;;kCAiBiB;QAC9B,MAAM,EAAE,uBAAuB;KAChC;IACD;QACE,IAAI,EAAE,gBAAgB;QACtB,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;gCAuBe;QAC5B,MAAM,EAAE,0BAA0B;KACnC;IACD;QACE,IAAI,EAAE,eAAe;QACrB,WAAW,EAAE;;;;;;;;;;;;;;;;;gCAiBe;QAC5B,MAAM,EAAE,yBAAyB;KAClC;IACD;QACE,IAAI,EAAE,cAAc;QACpB,WAAW,EAAE;;;;;;;;;;;;;;;;;kCAiBiB;QAC9B,MAAM,EAAE,wBAAwB;KACjC;IACD;QACE,IAAI,EAAE,sBAAsB;QAC5B,WAAW,EAAE;;;;;;;;;;;;;;;;wBAgBO;QACpB,MAAM,EAAE,+BAA+B;KACxC;IACD;QACE,IAAI,EAAE,uBAAuB;QAC7B,WAAW,EAAE;;;;;;;;;;;;;;;;gCAgBe;QAC5B,MAAM,EAAE,CAAC,CAAC,MAAM,CAAC,EAAE,CAAC,EAAE,QAAQ;KAC/B;CACF,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yeepay/coderocket-mcp",
-  "version": "1.2.4",
+  "version": "1.2.6",
   "description": "CodeRocket MCP - Independent AI-powered code review server for Model Context Protocol",
   "main": "dist/index.js",
   "type": "module",
@@ -27,7 +27,6 @@
     "code-review",
     "ai",
     "gemini",
-    "opencode",
     "claudecode",
     "typescript",
     "code-analysis",
@@ -46,8 +45,10 @@
     "@anthropic-ai/sdk": "^0.27.0",
     "@google/generative-ai": "^0.21.0",
     "@modelcontextprotocol/sdk": "^0.5.0",
+    "@yeepay/coderocket-mcp": "^1.2.5",
     "axios": "^1.6.0",
-    "zod": "^3.22.4"
+    "zod": "^3.22.4",
+    "zod-to-json-schema": "^3.24.6"
   },
   "devDependencies": {
     "@eslint/js": "^9.32.0",

package/review_logs/review-2eacf48a.md

@@ -0,0 +1,69 @@
+# 代码审查报告：feat: 统一提示词系统实现
+
+**Commit Hash**: `2eacf48a6028d5fd8c4ee5d950618145520bebd2`
+
+## 审阅状态
+
+✅ **通过**
+
+## 总体评价
+
+本次提交高质量地完成了一项重要的重构任务：**统一提示词系统**。
+
+代码修改清晰、目标明确，并且通过添加测试用例和更新文档确保了变更的可靠性和可维护性。这是一个优秀的提交，提升了项目的一致性和可扩展性。
+
+## 审阅维度分析
+
+### 1. 功能完整性与正确性
+
+*   **逻辑正确性**:
+    *   **[通过]** `PromptManager` 的重构逻辑正确，成功移除了旧的 `code-review-prompt`，并将所有审查功能（`reviewCode`, `reviewFile`）统一指向 `git-commit-review-prompt`。
+    *   **[通过]** 内置的 `git-commit-review-prompt` 提示词内容经过了优化，使其更具通用性，能够覆盖所有代码审查场景，而不仅仅是 Git Commit 审查。
+*   **功能实现**:
+    *   **[通过]** 完全实现了 Commit Message 中描述的目标，成功统一了提示词系统。
+    *   **[通过]** `preloadCommonPrompts` 的逻辑也同步更新，不再预加载已移除的提示词，提高了启动效率。
+*   **错误处理**:
+    *   **[符合预期]** 本次修改未引入新的错误处理逻辑，现有逻辑保持不变。
+
+### 2. 代码质量与规范
+
+*   **代码规范**:
+    *   **[通过]** 代码遵循了项目既定的 Prettier 格式化标准和命名约定。
+*   **可读性与可维护性**:
+    *   **[优秀]** 移除冗余的提示词并统一接口，极大地提高了代码的可读性和可维护性。未来维护提示词只需修改一个地方，降低了心智负担。
+*   **注释质量**:
+    *   **[优秀]** `test.ts` 中新增的测试用例 `testUnifiedPromptUsage` 包含了清晰的注释，准确描述了测试意图。
+
+### 3. 健壮性与风险
+
+*   **安全性**:
+    *   **[符合预期]** 本次修改不涉及安全相关内容。
+*   **性能**:
+    *   **[优秀]** `preloadCommonPrompts` 只加载必要的提示词，轻微提升了应用的冷启动性能。
+*   **资源管理**:
+    *   **[符合预期]** 本次修改不涉及资源管理。
+
+### 4. 测试与文档
+
+*   **可测试性**:
+    *   **[优秀]** 新增了专门的 `testUnifiedPromptUsage` 测试用例，用于验证统一提示词系统的正确性。测试覆盖了内置提示词的内容、加载机制和统一性，确保了重构的可靠性。
+*   **文档完整性**:
+    *   **[优秀]** `README.md` 中新增了“提示词自定义”章节，详细说明了统一提示词的优先级、自定义方法和优势。
+    *   **[优秀]** `CHANGELOG.md` 记录了清晰、完整的变更历史。
+
+### 5. 架构与扩展性
+
+*   **设计合理性**:
+    *   **[优秀]** 将所有审查功能收敛到单一提示词模板，是优秀的设计决策。它简化了系统架构，增强了功能的一致性。
+*   **扩展性**:
+    *   **[优秀]** 统一的提示词系统为未来扩展新的审查功能（如审查一个目录、一个函数等）奠定了坚实的基础，新功能可以轻松复用现有的提示词逻辑。
+
+## 优秀实践识别
+
+1.  **测试驱动重构**: 在进行重构的同时，编写了专门的测试用例来验证其正确性，这是保证代码质量的最佳实践。
+2.  **文档同步更新**: 任何对用户或开发者有影响的变更，都及时、清晰地更新了 `README.md` 和 `CHANGELOG.md`，值得称赞。
+3.  **简化优于复杂**: 移除了冗余代码和配置，用更简单的方案解决了问题，提升了系统的可维护性。
+
+## 结论
+
+此次提交堪称典范，建议合并。

package/review_logs/review-d3bd2f0.md

@@ -0,0 +1,35 @@
+# Code Review Report for commit d3bd2f0d87d13d0584477df3bc9554959e0d041f
+
+**Commit Author:** im47cn <dremabt@gmail.com>
+**Commit Date:** Fri Aug 1 16:32:24 2025 +0800
+**Commit Message:** feat: 移除对OpenCode服务的支持，更新相关文档和测试用例
+
+## Overall Assessment
+
+This is a solid commit that effectively removes the OpenCode service from the project. The changes are consistent across the codebase, including documentation, examples, and configuration, which demonstrates thoroughness.
+
+## Detailed Review
+
+### `README.md`
+- **Change:** Removed references to `OPENCODE_API_KEY` and the OpenCode service.
+- **Assessment:** Correct and necessary change.
+
+### `examples/usage-examples.md`
+- **Change:** Updated examples to use `gemini` instead of `opencode` and removed `opencode` from a status example.
+- **Assessment:** Good. This ensures the examples are up-to-date with the current state of the codebase.
+
+### `package.json`
+- **Change:** Removed `opencode` from the keywords.
+- **Assessment:** Good. This is a nice touch for keeping the package metadata clean.
+
+### `src/coderocket.ts`
+- **Change:** Removed `OPENCODE_API_KEY` from the list of environment variables.
+- **Assessment:** Correct. This is the core change to remove the service's configuration.
+
+### `src/test.ts`
+- **Change:** Removed the assertion `!serviceNames.includes('opencode' as any)`.
+- **Assessment:** This change is slightly concerning. While the test might have become redundant if the underlying code now completely filters out 'opencode', removing a test that explicitly checks for the removal of a feature is counter-intuitive. It would have been better to keep the test to ensure the service is not accidentally re-introduced in the future. However, this is a minor point and does not break any functionality.
+
+## Conclusion
+
+The commit is approved. The changes are well-executed and complete.

package/review_logs/review-d6c54600.md

@@ -0,0 +1,28 @@
+# Code Review Report
+
+**Commit:** `d6c546005f337299aeaf7fc61c7bb610c1359bac`
+**Author:** im47cn <dremabt@gmail.com>
+**Date:** Fri Aug 1 18:52:45 2025 +0800
+**Subject:** chore: 升级版本到 1.2.5
+
+## 1. Review Summary
+
+The commit is a routine version update, changing the version number in `package.json` from `1.2.4` to `1.2.5`. The changes are consistent with the commit message.
+
+## 2. Code Changes Analysis
+
+- **File:** `package.json`
+- **Change:** The `version` field was updated from "1.2.4" to "1.2.5".
+
+## 3. Guideline Compliance (`CRUSH.md`)
+
+- **Commit Message:** The commit message `chore: 升级版本到 1.2.5` is clear and correctly uses the "chore" type for a maintenance task, which aligns with conventional commit standards.
+- **Code Style:** The change is in a `package.json` file and the modification is syntactically correct. No other code style rules from `CRUSH.md` are applicable to this change.
+- **Overall:** The commit is simple, straightforward, and adheres to all relevant project guidelines.
+
+## 4. Conclusion
+
+This commit is approved. It is a standard and necessary change for version management.
+
+---
+*This review was generated automatically.*

package/review_logs/review-report-5767eab8.md

@@ -0,0 +1,33 @@
+# Code Review Report for Commit 5767eab8
+
+**Commit Author:** im47cn <dremabt@gmail.com>
+**Commit Date:** Fri Aug 1 19:32:16 2025 +0800
+**Commit Message:** fix: 修复ES模块导入路径问题
+
+---
+
+## 1. Review Summary
+
+The commit primarily addresses an ES module import path issue, which is a valid and necessary fix for compatibility. The change in `src/toolDefinitions.ts` aligns with the project's coding standards.
+
+However, the changes in `package.json` and `package-lock.json` introduce a self-dependency, which is highly unusual and likely an error. This could lead to problems with package resolution and management.
+
+## 2. Changes Analysis
+
+### `src/toolDefinitions.ts`
+
+*   **Change:** The import path for `./types` was changed to `./types.js`.
+*   **Assessment:** **Positive**. This change correctly follows the guidelines in `CRUSH.md` which state: "Add a `.js` extension to relative imports". This resolves a runtime module loading error in an ES module context.
+
+### `package.json` and `package-lock.json`
+
+*   **Change:** The package `@yeepay/coderocket-mcp` was added as a dependency to itself.
+*   **Assessment:** **Potential Issue**. This is not a standard practice and should be investigated. It might be a mistake made during dependency updates. Self-dependencies can create circular resolution problems and are generally unnecessary.
+
+## 3. Actionable Recommendations
+
+*   **Recommendation:** Revert the changes in `package.json` and `package-lock.json` that introduce the self-dependency. The version bump is acceptable, but the dependency itself should be removed.
+*   **Action:** The change in `src/toolDefinitions.ts` is correct and should be kept.
+
+---
+*This report was generated automatically.*

package/review_logs/review-fc88c611.md

@@ -1,74 +0,0 @@
-# Code Review Report for Commit `fc88c611ec9b`
-
-**Commit Author:** `im47cn <dremabt@gmail.com>`
-**Commit Date:** `Fri Aug 1 15:41:41 2025 +0800`
-**Commit Message:**
-```
-fix: 移除自引用依赖，确保完全独立
-
-🔧 关键修复：
-- 移除 package.json 中的自引用依赖 @yeepay/coderocket-mcp
-- 修复可能导致安装问题的循环依赖
-- 确保依赖列表只包含必要的外部包
-
-✅ 独立性验证：
-- 系统性排查确认零 coderocket-cli 依赖
-- 所有 shell 命令都是标准 Git 操作
-- 使用独立的 ~/.coderocket/ 配置目录
-- 所有功能通过直接 API 调用实现
-
-🧪 质量保证：
-- 100% 测试通过率 (9/9)
-- Git 变更检测和 AI 审查功能正常
-- 无破坏性变更，保持向后兼容
-
-📦 版本发布：
-- 版本号：v1.2.3
-- NPM发布：@yeepay/coderocket-mcp@1.2.3
-- 完全独立的 MCP 服务器
-```
-
----
-
-## 1. Review Summary
-
-This is an **excellent** and crucial fix that addresses a critical circular dependency issue. The change is well-executed, and the developer has been exceptionally thorough in updating all related parts of the project, including documentation and versioning.
-
-**Overall Assessment:** ✅ **Approve**
-
----
-
-## 2. Analysis of Changes
-
-### 2.1. Dependency Fix (`package.json`, `package-lock.json`)
-
-- **[Positive]** The primary goal of removing the `@yeepay/coderocket-mcp` self-reference from `dependencies` has been successfully achieved. This resolves a significant packaging flaw that could lead to installation failures and versioning conflicts.
-- **[Positive]** The `package-lock.json` file has been correctly updated to reflect this change.
-- **[Positive]** The package version was correctly bumped to `1.2.3`, following semantic versioning for a patch fix.
-
-### 2.2. Documentation and Consistency (`README.md`, `CHANGELOG.md`, `examples/usage-examples.md`)
-
-- **[Positive]** The `CHANGELOG.md` is updated with a clear, well-formatted entry for version `1.2.3`. The description of the fix is detailed and easy to understand.
-- **[Positive]** The `README.md` has been updated to remove incorrect statements about dependencies (e.g., the note about needing `CodeRocket-CLI`). This improves user clarity and accuracy.
-- **[Positive]** Other documentation files (`examples/usage-examples.md`) have also been updated for consistency.
-
-### 2.3. Source Code (`src/*.ts`)
-
-- **[Positive]** Fallback and default version numbers in `src/banner.ts` and `src/index.ts` have been updated to `1.2.3`, ensuring consistency with the `package.json` version.
-
----
-
-## 3. Adherence to Project Guidelines (`CRUSH.md`)
-
-- **[Positive]** **Code Style & Formatting:** The changes adhere to the project's style.
-- **[Positive]** **Clarity:** The commit message is exemplary. It is highly detailed, structured, and clearly communicates the purpose, scope, and verification of the change. This level of detail is incredibly helpful for future maintenance.
-- **[Positive]** **Thoroughness:** The developer demonstrated great attention to detail by updating not just the code, but all user-facing documentation and changelogs.
-
----
-
-## 4. Suggestions for Improvement
-
-- **None.** This commit is a model example of a high-quality contribution. It is comprehensive, well-documented, and correctly executed.
-
----
-**End of Report**