ai-project-manage-cli 6.0.81 → 6.0.82

package/dist/index.js

@@ -4265,6 +4265,42 @@ function posixBasename(p) {
   return idx >= 0 ? normalized.slice(idx + 1) : normalized;
 }
 
+// src/commands/deploy/internal/deploy-hints.ts
+function formatDeployNotConfiguredLines(env, deployCommands) {
+  const configuredEnvs = Object.keys(deployCommands).filter(
+    (key) => deployCommands[key]?.trim()
+  );
+  if (configuredEnvs.length > 0) {
+    return [
+      `[apm] \u65E0\u6CD5\u6267\u884C\u90E8\u7F72\uFF1Aapm.config.json \u4E2D\u672A\u914D\u7F6E deploy.${env}`,
+      `[apm] \u5F53\u524D\u5DF2\u914D\u7F6E\u7684\u73AF\u5883: ${configuredEnvs.join(", ")}`
+    ];
+  }
+  return [
+    "[apm] \u65E0\u6CD5\u6267\u884C\u90E8\u7F72\uFF1A\u5F53\u524D\u9879\u76EE\u672A\u914D\u7F6E\u81EA\u52A8\u5316\u90E8\u7F72\uFF08apm.config.json \u4E2D\u65E0 deploy \u6BB5\uFF09",
+    "[apm] \u90E8\u5206\u9879\u76EE\u4E0D\u652F\u6301\u6216\u672A\u542F\u7528\u81EA\u52A8\u5316\u90E8\u7F72\uFF0C\u5C5E\u6B63\u5E38\u60C5\u51B5\uFF0C\u53EF\u8DF3\u8FC7\u90E8\u7F72"
+  ];
+}
+function formatWisdomFrontendDeployNotConfiguredLines(env, packageJsonPath) {
+  return [
+    `[apm] \u65E0\u6CD5\u6267\u884C\u90E8\u7F72\uFF1A${packageJsonPath} \u4E2D\u672A\u627E\u5230 deploy:${env} \u811A\u672C`,
+    "[apm] \u82E5\u672C\u9879\u76EE\u4E0D\u652F\u6301\u81EA\u52A8\u5316\u90E8\u7F72\uFF0C\u5C5E\u6B63\u5E38\u60C5\u51B5\uFF0C\u53EF\u8DF3\u8FC7\u90E8\u7F72"
+  ];
+}
+function printDeployNotConfiguredHint(env, deployCommands) {
+  for (const line of formatDeployNotConfiguredLines(env, deployCommands)) {
+    console.error(line);
+  }
+}
+function printWisdomFrontendDeployNotConfiguredHint(env, packageJsonPath) {
+  for (const line of formatWisdomFrontendDeployNotConfiguredLines(
+    env,
+    packageJsonPath
+  )) {
+    console.error(line);
+  }
+}
+
 // src/commands/deploy/internal/wisdom-auto-deploy.ts
 import { existsSync as existsSync17, readFileSync as readFileSync14 } from "node:fs";
 import path3 from "node:path";
@@ -5089,8 +5125,9 @@ async function runWisdomAutoDeploy(options) {
   if (projectType === "frontend") {
     const deployCmd = resolveFrontendDeployCommand(options.env, cwd);
     if (!deployCmd) {
-      console.error(
-        `\u524D\u7AEF\u9879\u76EE ${path3.join(cwd, "package.json")} \u4E2D\u672A\u627E\u5230 deploy:${options.env} \u811A\u672C`
+      printWisdomFrontendDeployNotConfiguredHint(
+        options.env,
+        path3.join(cwd, "package.json")
       );
       process.exit(1);
     }
@@ -5142,12 +5179,7 @@ function registerDeployMainCommand(program) {
     const deployCommands = cfg.deploy ?? {};
     const command = deployCommands[env]?.trim();
     if (!command) {
-      const keys = Object.keys(deployCommands);
-      console.error(
-        keys.length > 0 ? `apm.config.json \u4E2D\u672A\u914D\u7F6E deploy.${env}\uFF0C\u53EF\u7528\u73AF\u5883: ${keys.join(
-          ", "
-        )}` : `apm.config.json \u4E2D\u672A\u914D\u7F6E deploy \u6BB5`
-      );
+      printDeployNotConfiguredHint(env, deployCommands);
       process.exit(1);
     }
     runShellCommand3(command, cwd);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-project-manage-cli",
-  "version": "6.0.81",
+  "version": "6.0.82",
   "description": "命令行工具：后续用于调用平台后端 API 完成运维与自动化操作",
   "type": "module",
   "private": false,

package/template/skills/apm-deploy/SKILL.md

@@ -1,8 +1,14 @@
+# apm-deploy：自动化部署
+
 ## 工作流程
 
-在项目根目录执行 `apm deploy <环境名称>`
+在项目根目录执行 `apm deploy <环境名称>`，**以命令执行结果为准**：
+
+- **成功**：部署完成，在回信中说明测试环境地址或部署结果。
+- **失败且输出含「未配置自动化部署」或「可跳过部署」**：本项目不支持自动化部署，属正常情况；放弃部署，在回信说明已跳过即可，无需修复配置或重试。
+- **其他失败**：按输出排查并修复后重试。
 
 ## 示例
 
 1. 部署测试环境：`apm deploy test`
-2. 部署正式环境: `apm deploy online`
+2. 部署正式环境：`apm deploy online`

package/template/skills/apm-dev/SKILL.md

@@ -86,7 +86,7 @@ ALTER TABLE inspection_class ADD COLUMN is_project_add VARCHAR(1) DEFAULT '0';
 开发完成的定义是以下三项**全部满足**，缺一不可：
 
 1. **构建通过**：执行本仓库的构建/检查命令（见 AGENTS.md 或部署文档），失败必须修复后重试。
-2. **发布测试环境**：**Read** `.apm/skills/apm-deploy/SKILL.md` 并按其流程部署；**后端**涉及 SQL 变更时，须在回复中引用 `docs/SQL.md`，并写明待执行的 SQL 文件名或执行顺序。
+2. **发布测试环境**：**Read** `.apm/skills/apm-deploy/SKILL.md` 并按其流程执行 `apm deploy`（以命令结果判断是否跳过）；**后端**涉及 SQL 变更时，须在回复中引用 `docs/SQL.md`，并写明待执行的 SQL 文件名或执行顺序。
 3. **白名单对账**：在回复中逐文件列出本次改动与计划白名单的对应关系。
 
 **注意：不做联调。** 前后端各自按 `API.md` 交付，接口对不上属于契约或实现问题，由 diff 评审与人工验收暴露后打回修复；禁止自行发起「联调」「接口实测」类的开放式动作。