@d5render/cli 0.1.87 → 0.1.89

package/.skills/code-review/SKILL.md

@@ -1,38 +1,37 @@
----
-name: code-review
-description: code-review task process.
----
-
-For all review-related tasks, the subagent and main-agent can confirm with each other without user confirmation; they can be executed directly. However, it is important to note that all executed tasks must be listed at the end and only main-agent can execute report tasks. And obtain as much context as possible, including but not limited to the following:
-
-- Use tools to locate files related to the changes. However, commits that explicitly request a merge, such as those with the title "Merge", do not require processing.
-- Use toolchains to build complete call relationships and flowcharts for diff code, ensure the relevant graphs are as complete as possible (use `LSP` tool as a first-choice solution, and try other toolchain only if encounter problems). And use other tools mentioned in related documents to construct a data flow graph of the changes, ensure the relevant graphs are as complete as possible.
-
-Then,
-
-- Launch parallel subagents to independently code review the change (Unless there are special requirements, only the main-agent needs to call the report mcp tools, subagnets do not call.). Information can be communicated between the subagents and main-agent, Subagents should do the following, then return a list of issues and the reason each issue was flagged (eg. .md adherence, issue, historical git context, etc.):
-  - One of:
-    - Read README.md, AGENTS.md, .github/**.md, .cursor/**.md files in the **same directory** as the changes and the **root directory**.
-    - Determining whether documents contain related content requires additional loading and returning to the main agent.
-    - Check [severity.instructions.md](./severity.instructions.md) to clarify error severity levels, Please follow the project requirements regarding the redefinition of error levels in the relevant documentation.
-  - Another of:
-    - Read all modified codes block, build a complete data flow and call relationship graph about the codes to review logic
-    - Consider whether there is a better implementation for the current logic.
-  - One more of:
-    - Read the git blame and history of the code modified, to identify any issues in light of that historical context
-    - Read code comments in the modified files, and make sure the changes in the pull request comply with any guidance in the comments.
-    - Read previous pull requests that touched these files, and check for any comments on those pull requests that may also apply to the current pull request.
-    - Consider other related aspects of the current function and provide corresponding suggestions.
-- Parallel subagents have the following additions.
-  - The subagents **should not** perform any report-related tasks.
-  - For each issue found returns a score to indicate the agent's level of confidence for whether the issue is real or false positive. To do that, the agent should score each issue on a scale from 0-100, indicating its level of confidence. For issues that were flagged due to CLAUDE.md instructions, the agent should double check that the CLAUDE.md actually calls out that issue specifically. The scale is (give this rubric to the agent verbatim):
-    - 0: Not confident at all. This is a false positive that doesn't stand up to light scrutiny, or is a pre-existing issue.
-    - 25: Somewhat confident. This might be a real issue, but may also be a false positive. The agent wasn't able to verify that it's a real issue. If the issue is stylistic, it is one that was not explicitly called out in the relevant CLAUDE.md.
-    - 50: Moderately confident. The agent was able to verify this is a real issue, but it might be a nitpick or not happen very often in practice. Relative to the rest of the PR, it's not very important.
-    - 75: Highly confident. The agent double checked the issue, and verified that it is very likely it is a real issue that will be hit in practice. The existing approach in the PR is insufficient. The issue is very important and will directly impact the code's functionality, or it is an issue that is directly mentioned in the relevant CLAUDE.md.
-    - 100: Absolutely certain. The agent double checked the issue, and confirmed that it is definitely a real issue, that will happen frequently in practice. The evidence directly confirms this.
-  - List the task plan and output the task completion status to main-agent. Then, main-agent performs the following actions
-- First, based on the report, relevant tools were used again to supplement the context, them evaluate codes self.
-- Then, compare and organize the issue scores in self and subagent, refine the context of projects scoring below 60, and re-perform the review. And final score is the average of the three scores.
-- List all the task status
-- Executes the report-related processes, must use chinese(中文) to report
+---
+name: code-review
+description: code-review task process for main-agent, subagent please not call report tools.
+---
+
+For all review-related tasks, the subagent and main-agent can confirm with each other without user confirmation; they can be executed directly. However, it is important to note that all executed tasks must be listed at the end and only main-agent can execute report tasks. And obtain as much context as possible, including but not limited to the following:
+
+- Use tools to locate files related to the changes. However, commits that explicitly request a merge, such as those with the title "Merge", do not require processing.
+- Use toolchains to build complete call relationships and flowcharts for diff code, ensure the relevant graphs are as complete as possible (use `LSP` tool as a first-choice solution, and try other toolchain only if encounter problems). And use other tools mentioned in related documents to construct a data flow graph of the changes, ensure the relevant graphs are as complete as possible.
+
+Then,
+
+- Launch parallel subagents to independently code review the change (Unless there are special requirements, only the main-agent needs to call the report mcp tools, subagents do not call.). Information can be communicated between the subagents and main-agent, Subagents should do the following, then return a list of issues and the reason each issue was flagged (eg. .md adherence, issue, historical git context, etc.):
+  - One of:
+    - Read README.md, AGENTS.md, .github/**.md, .cursor/**.md files in the **same directory** as the changes and the **root directory**.
+    - Read code comments in the modified files, and make sure the changes in the pull request comply with any guidance in the comments.
+    - Determining whether documents contain related content requires additional loading and returning to the main agent.
+    - Check [severity.instructions.md](./severity.instructions.md) to clarify error severity levels, Please follow the project requirements regarding the redefinition of error levels in the relevant documentation.
+  - Another of:
+    - Read all modified codes block, build a complete data flow and call relationship graph about the codes to review logic
+    - Consider whether there is a better implementation for the current logic.
+  - One more of: Read the Git messages and modification history chronologically
+    - Identify issues by incorporating commit history.
+    - Consider other related aspects of the current function and provide corresponding suggestions.
+- Parallel subagents have the following additions.
+  - The subagents **should not** perform any report-related tasks.
+  - For each issue found returns a score to indicate the agent's level of confidence for whether the issue is real or false positive. To do that, the agent should score each issue on a scale from 0-100, indicating its level of confidence. For issues that were flagged due to CLAUDE.md instructions, the agent should double check that the CLAUDE.md actually calls out that issue specifically. The scale is (give this rubric to the agent verbatim):
+    - 0: Not confident at all. This is a false positive that doesn't stand up to light scrutiny, or is a pre-existing issue.
+    - 25: Somewhat confident. This might be a real issue, but may also be a false positive. The agent wasn't able to verify that it's a real issue. If the issue is stylistic, it is one that was not explicitly called out in the relevant CLAUDE.md.
+    - 50: Moderately confident. The agent was able to verify this is a real issue, but it might be a nitpick or not happen very often in practice. Relative to the rest of the PR, it's not very important.
+    - 75: Highly confident. The agent double checked the issue, and verified that it is very likely it is a real issue that will be hit in practice. The existing approach in the PR is insufficient. The issue is very important and will directly impact the code's functionality, or it is an issue that is directly mentioned in the relevant CLAUDE.md.
+    - 100: Absolutely certain. The agent double checked the issue, and confirmed that it is definitely a real issue, that will happen frequently in practice. The evidence directly confirms this.
+  - List the task plan and output the task completion status to main-agent. Then, main-agent performs the following actions
+- First, based on the report, relevant tools were used again to supplement the context, them evaluate codes self.
+- Then, compare and organize the issue scores in self and subagent, refine the context of projects scoring below 60, and re-perform the review. And final score is the average of the three scores.
+- List all the task status
+- Executes the report-related processes, must use chinese(中文) to report

package/bin/d5cli

@@ -1,14 +1,15 @@
 #!/usr/bin/env node
-import { argv, env, platform } from "node:process";
+import { argv, cwd, env, platform } from "node:process";
 import { execSync, spawn } from "node:child_process";
 import { createHash } from "node:crypto";
 import { copyFileSync, existsSync, mkdirSync, readFileSync, readdirSync, writeFileSync } from "node:fs";
+import { tmpdir } from "node:os";
 import { dirname, join } from "node:path";
 import { fileURLToPath } from "node:url";
 
 //#region package.json
 var name$1 = "@d5render/cli";
-var version = "0.1.87";
+var version = "0.1.89";
 
 //#endregion
 //#region packages/env.ts
@@ -29,7 +30,6 @@ const envConfigKeys = [
 	"CI_MERGE_REQUEST_IID",
 	"CI_MERGE_REQUEST_TITLE",
 	"CI_MERGE_REQUEST_DESCRIPTION",
-	"JIRA_BASE_URL",
 	"DINGTALK_WEBHOOK",
 	"GITLAB_TOKEN",
 	"JIRA_PAT",
@@ -39,7 +39,7 @@ const envConfigKeys = [
 	"TOKEN_USAGE"
 ];
 const envUsed = Object.defineProperty({}, "JIRA_BASE_URL", {
-	get: () => toEnv("CI_SERVER_URL", "http://jira.d5techs.com.cn"),
+	get: () => toEnv("JIRA_BASE_URL", "http://jira.d5techs.com.cn"),
 	enumerable: true,
 	configurable: true
 });
@@ -126,16 +126,17 @@ async function sendding(title, text) {
 //#region review/helper.ts
 const NAME = name$1.replaceAll("/", "_");
 const VERSION = version;
-const TEMP = join(env.CI_PROJECT_DIR || "", `../../.${NAME}`);
+const CWD = env.CI_PROJECT_DIR || cwd();
+const TEMP = join(tmpdir(), `.${NAME}`);
 const common_review_prompt = `Load code-review skills, then call the mcp tool '${name}-${getHash}' to load code-review commits.
 Then use chinese(中文) to call the mcp tool '${name}-${report}', only main agent can call the tool '${name}-${report}', **prevent** subagent from calling tool '${name}-${report}`;
 async function changelog() {
-	const changelog = readFileSync(join(RUNTIME_CWD, "README.md"), "utf8");
-	const cachepath = join(TEMP, "CHANGELOG_" + createHash("md5").update(env.DINGTALK_WEBHOOK || env.CI_RUNNER_ID || env.CI_PROJECT_ID || "").digest("hex"));
-	if (changelog === (existsSync(cachepath) ? readFileSync(cachepath, "utf8") : "")) return;
 	if (!existsSync(TEMP)) mkdirSync(TEMP, { recursive: true });
+	const changelog = readFileSync(join(RUNTIME_CWD, "README.md"), "utf8");
+	const cachepath = join(TEMP, "CHANGELOG_" + createHash("md5").update(env.DINGTALK_WEBHOOK || env.CI_RUNNER_ID || env.CI_PROJECT_ID || "").digest("hex")), feedback_cachepath = join(env.CI_PROJECT_DIR || "", `../../.${NAME}`);
+	if (changelog === (existsSync(cachepath) ? readFileSync(cachepath, "utf8") : existsSync(feedback_cachepath) ? readFileSync(feedback_cachepath, "utf8") : "")) return;
 	writeFileSync(cachepath, changelog, "utf8");
-	console.log("updated CHANGELOG cache.");
+	console.log("updated CHANGELOG cache...");
 	let matched = changelog.match(/CHANGELOG[\s\S]*?(#+[^\n]*\n+([\s\S]*?))(?=#+|$)/)?.[1] ?? "";
 	const matcheds = matched.split("\n");
 	matcheds.shift();
@@ -325,7 +326,7 @@ async function cli() {
 	];
 	let child;
 	if (platform === "win32") child = spawn(bin, args, {
-		cwd: env.CI_PROJECT_DIR,
+		cwd: CWD,
 		stdio: [
 			"inherit",
 			"pipe",
@@ -334,7 +335,7 @@ async function cli() {
 		shell: true
 	});
 	else child = spawn("sh", ["-c", `export GH_TOKEN=${shellEscape(env.GH_TOKEN)}; exec ${bin} ${args.map((a) => shellEscape(a)).join(" ")}`], {
-		cwd: env.CI_PROJECT_DIR,
+		cwd: CWD,
 		stdio: [
 			"inherit",
 			"pipe",

package/bin/mcpServer.js

@@ -18961,7 +18961,6 @@ const envConfigKeys = [
 	"CI_MERGE_REQUEST_IID",
 	"CI_MERGE_REQUEST_TITLE",
 	"CI_MERGE_REQUEST_DESCRIPTION",
-	"JIRA_BASE_URL",
 	"DINGTALK_WEBHOOK",
 	"GITLAB_TOKEN",
 	"JIRA_PAT",
@@ -18971,7 +18970,7 @@ const envConfigKeys = [
 	"TOKEN_USAGE"
 ];
 const envUsed = Object.defineProperty({}, "JIRA_BASE_URL", {
-	get: () => toEnv("CI_SERVER_URL", "http://jira.d5techs.com.cn"),
+	get: () => toEnv("JIRA_BASE_URL", "http://jira.d5techs.com.cn"),
 	enumerable: true,
 	configurable: true
 });

package/package.json

@@ -1,40 +1,40 @@
-{
-  "name": "@d5render/cli",
-  "version": "0.1.87",
-  "license": "MIT",
-  "author": "jasirou",
-  "bin": {
-    "d5cli": "bin/d5cli"
-  },
-  "files": [
-    "CHANGELOG.md",
-    ".skills/code-review",
-    ".skills/devops",
-    "bin/d5cli",
-    "bin/mcpServer.js",
-    ".github/instructions/severity.instructions.md"
-  ],
-  "type": "module",
-  "main": "./bin/d5cli",
-  "dependencies": {
-    "vscode-languageserver-protocol": "^3.17.5"
-  },
-  "devDependencies": {
-    "@modelcontextprotocol/sdk": "^1.25.3",
-    "@types/node": "^25.1.0",
-    "@types/vscode": "^1.108.1",
-    "@vscode/vsce": "^3.7.1",
-    "json5": "^2.2.3",
-    "oxfmt": "^0.21.0",
-    "oxlint": "^1.42.0",
-    "rolldown": "1.0.0-rc.2",
-    "vitest": "^4.0.18",
-    "zod": "^4.3.6"
-  },
-  "scripts": {
-    "build": "node ./setup.js build",
-    "release": "node ./setup.js publish",
-    "setup": "node ./setup.js",
-    "test": "node ./setup.js build:development"
-  }
-}
+{
+  "name": "@d5render/cli",
+  "version": "0.1.89",
+  "license": "MIT",
+  "author": "jasirou",
+  "bin": {
+    "d5cli": "bin/d5cli"
+  },
+  "files": [
+    "CHANGELOG.md",
+    ".skills/code-review",
+    ".skills/devops",
+    "bin/d5cli",
+    "bin/mcpServer.js",
+    ".github/instructions/severity.instructions.md"
+  ],
+  "type": "module",
+  "main": "./bin/d5cli",
+  "scripts": {
+    "build": "node ./setup.js build",
+    "release": "node ./setup.js publish",
+    "setup": "node ./setup.js",
+    "test": "node ./setup.js build:development"
+  },
+  "dependencies": {
+    "vscode-languageserver-protocol": "^3.17.5"
+  },
+  "devDependencies": {
+    "@modelcontextprotocol/sdk": "^1.25.3",
+    "@types/node": "^25.1.0",
+    "@types/vscode": "^1.108.1",
+    "@vscode/vsce": "^3.7.1",
+    "json5": "^2.2.3",
+    "oxfmt": "^0.21.0",
+    "oxlint": "^1.42.0",
+    "rolldown": "1.0.0-rc.2",
+    "vitest": "^4.0.18",
+    "zod": "^4.3.6"
+  }
+}