@d5render/cli 0.1.56 → 0.1.60

package/bin/d5cli

@@ -1,6 +1,5 @@
 #!/usr/bin/env node
 import { execSync, spawn } from "node:child_process";
-import { createConnection } from "node:net";
 import { copyFileSync, existsSync, mkdirSync, readFileSync, readdirSync, rmSync, writeFileSync } from "node:fs";
 import { dirname, join } from "node:path";
 import { argv, env, platform } from "node:process";
@@ -52,9 +51,9 @@ function toEnv(key, defaultValue) {
 }
 function buildEnv() {
 	const envArg = argv.find((arg) => arg.startsWith("--customizenv="));
-	let envJson$1 = {};
-	if (envArg) envJson$1 = JSON.parse(envArg.replace("--customizenv=", ""));
-	return envJson$1;
+	let envJson = {};
+	if (envArg) envJson = JSON.parse(envArg.replace("--customizenv=", ""));
+	return envJson;
 }
 
 //#endregion
@@ -108,7 +107,7 @@ function installCopilot() {
 //#endregion
 //#region package.json
 var name = "@d5render/cli";
-var version = "0.1.56";
+var version = "0.1.60";
 
 //#endregion
 //#region packages/gitlab/url.ts
@@ -221,14 +220,14 @@ async function deploy() {
 async function need() {
 	if (!env.CI) return true;
 	const { CI_MERGE_REQUEST_IID, CI_COMMIT_SHA } = env;
-	const file$1 = join(TEMP, "CODEREVIEW");
+	const file = join(TEMP, "CODEREVIEW");
 	if (CI_MERGE_REQUEST_IID) {
-		let appended = `${existsSync(file$1) ? readFileSync(file$1, "utf8") : ""}\n${CI_MERGE_REQUEST_IID}`.split("\n");
+		let appended = `${existsSync(file) ? readFileSync(file, "utf8") : ""}\n${CI_MERGE_REQUEST_IID}`.split("\n");
 		const max = 1e4;
 		if (appended.length > max) appended = appended.slice(-max);
 		if (!existsSync(TEMP)) mkdirSync(TEMP, { recursive: true });
-		writeFileSync(file$1, appended.join("\n"), "utf8");
-		console.log("merge pipeline, recorded IID:", CI_MERGE_REQUEST_IID, "to:", file$1);
+		writeFileSync(file, appended.join("\n"), "utf8");
+		console.log("merge pipeline, recorded IID:", CI_MERGE_REQUEST_IID, "to:", file);
 		return true;
 	}
 	if (!CI_COMMIT_SHA) return true;
@@ -239,7 +238,7 @@ async function need() {
 	}).toString().match(/See merge request[\s\S]+!(\d+)/);
 	if (!match) return true;
 	const iid = match[1];
-	const yes = (existsSync(file$1) ? readFileSync(file$1, "utf8") : "").split("\n").includes(iid);
+	const yes = (existsSync(file) ? readFileSync(file, "utf8") : "").split("\n").includes(iid);
 	if (yes) {
 		console.warn(`Merge Request !${iid} has been AI reviewed before.`);
 		const mergeURL = visitPipeline(iid).url;
@@ -273,7 +272,6 @@ async function codereview() {
 Otherwise, use chinese as default language to call the mcp tool '${name$1}-${report}'`;
 	const httpProxy = process.env.HTTP_PROXY || process.env.http_proxy || "";
 	const httpsProxy = process.env.HTTPS_PROXY || process.env.https_proxy || "";
-	await logProxyStatus(httpProxy, httpsProxy);
 	const copilot = spawn("node", [
 		findCopilopt(),
 		...tools,
@@ -301,108 +299,6 @@ Otherwise, use chinese as default language to call the mcp tool '${name$1}-${rep
 		copilot.on("close", (code) => res());
 	});
 }
-/** 代理排查：环境变量 + 检测代理是否在运行、子进程是否会走代理 */
-async function logProxyStatus(httpProxy, httpsProxy) {
-	const tag = "[proxy]";
-	console.log(`${tag} -------- 代理排查 --------`);
-	const proxyKeys = Object.keys(process.env).filter((k) => /proxy/i.test(k));
-	if (proxyKeys.length > 0) console.log(`${tag} 当前进程里含 proxy 的环境变量名: ${proxyKeys.join(", ")}`);
-	else console.log(`${tag} 当前进程里没有任何含 proxy 的环境变量（GitLab 未传入或未生效）`);
-	console.log(`${tag} 当前进程 env: HTTP_PROXY = ${process.env.HTTP_PROXY ?? "(未设置)"}, http_proxy = ${process.env.http_proxy ?? "(未设置)"}`);
-	console.log(`${tag} 当前进程 env: HTTPS_PROXY = ${process.env.HTTPS_PROXY ?? "(未设置)"}, https_proxy = ${process.env.https_proxy ?? "(未设置)"}`);
-	console.log(`${tag} 传给子进程: HTTP_PROXY = ${httpProxy || "(空)"}, HTTPS_PROXY = ${httpsProxy || "(空)"}`);
-	const proxyUrl = httpsProxy || httpProxy;
-	if (!proxyUrl) {
-		console.log(`${tag} 结论: 未设置代理，子进程将直连外网，不会经代理`);
-		await logGitHubReachable(tag, false);
-		console.log(`${tag} ------------------------`);
-		return;
-	}
-	let host;
-	let port;
-	try {
-		const u = new URL(proxyUrl);
-		host = u.hostname || "127.0.0.1";
-		port = u.port ? parseInt(u.port, 10) : 7890;
-	} catch {
-		console.log(`${tag} 结论: 代理 URL 解析失败，子进程可能无法正确使用代理: ${proxyUrl}`);
-		console.log(`${tag} ------------------------`);
-		return;
-	}
-	const reachable = await checkPortReachable(host, port);
-	if (reachable) {
-		console.log(`${tag} 代理检测: ${host}:${port} 可连接，代理服务应在运行`);
-		logPortListener(port, tag);
-	} else {
-		console.log(`${tag} 代理检测: ${host}:${port} 无法连接，可能代理未启动或地址/端口错误`);
-		logPortListener(port, tag);
-	}
-	await logGitHubReachable(tag, !!proxyUrl);
-	if (reachable) console.log(`${tag} 结论: 子进程已继承代理环境变量，请求应能通过代理发出`);
-	else console.log(`${tag} 结论: 子进程虽有代理变量，但代理不可达，请求可能失败或直连`);
-	console.log(`${tag} ------------------------`);
-}
-function checkPortReachable(host, port, timeoutMs = 3e3) {
-	return new Promise((resolve) => {
-		const socket = createConnection(port, host, () => {
-			socket.destroy();
-			resolve(true);
-		});
-		socket.setTimeout(timeoutMs);
-		socket.on("timeout", () => {
-			socket.destroy();
-			resolve(false);
-		});
-		socket.on("error", () => resolve(false));
-	});
-}
-/** 打印指定端口上的监听进程（如 7890 上是 mihomo） */
-function logPortListener(port, tag) {
-	try {
-		if (platform === "win32") {
-			const out = execSync(`netstat -ano | findstr :${port}`, {
-				encoding: "utf8",
-				maxBuffer: 65536
-			});
-			console.log(`${tag} 端口 ${port} 监听情况 (netstat):\n${out.trim().split("\n").slice(0, 10).join("\n")}`);
-			return;
-		}
-		const lsof = execSync(`lsof -i :${port} 2>/dev/null`, {
-			encoding: "utf8",
-			maxBuffer: 65536
-		}).trim();
-		if (lsof) {
-			console.log(`${tag} 端口 ${port} 监听进程 (lsof):\n${lsof}`);
-			return;
-		}
-	} catch {}
-	try {
-		const ss = execSync(`ss -tlnp 2>/dev/null | grep :${port}`, {
-			encoding: "utf8",
-			maxBuffer: 65536
-		}).trim();
-		if (ss) console.log(`${tag} 端口 ${port} 监听进程 (ss):\n${ss}`);
-		else console.log(`${tag} 端口 ${port}: 无法获取监听进程 (无 lsof/ss 或无权限)`);
-	} catch {
-		console.log(`${tag} 端口 ${port}: 无法获取监听进程 (无 lsof/ss 或无权限)`);
-	}
-}
-/** 检测 GitHub 是否可访问（Node 内置 fetch 不走代理，此处为直连可达性） */
-async function logGitHubReachable(tag, proxySet) {
-	const url = "https://api.github.com";
-	const note = proxySet ? " (当前进程已设代理，但 Node fetch 不经过代理，此处为直连)" : " (直连)";
-	try {
-		const ac = new AbortController();
-		const t = setTimeout(() => ac.abort(), 1e4);
-		const res = await fetch(url, { signal: ac.signal });
-		clearTimeout(t);
-		const ok = res.ok || res.status === 403;
-		console.log(`${tag} GitHub 连通性${note}: ${ok ? "可调通" : "异常"} status=${res.status}`);
-	} catch (e) {
-		const msg = e instanceof Error ? e.message : String(e);
-		console.log(`${tag} GitHub 连通性${note}: 调不通 - ${msg}`);
-	}
-}
 function findCopilopt() {
 	let copilot = "";
 	try {

package/package.json

@@ -4,7 +4,7 @@
   "license": "MIT",
   "author": "jasirou",
   "main": "./bin/d5cli",
-  "version": "0.1.56",
+  "version": "0.1.60",
   "devDependencies": {
     "@modelcontextprotocol/sdk": "^1.25.1",
     "@types/node": "^25.0.3",
@@ -18,7 +18,6 @@
     "zod": "^4.3.5"
   },
   "files": [
-    ".github/instructions/code-review.instructions.md",
     ".github/instructions/severity.instructions.md",
     ".skills/devops",
     ".skills/code-review",

package/.github/instructions/code-review.instructions.md

@@ -1,43 +0,0 @@
----
-applyTo: "**"
-excludeAgent: ["code-review"]
----
-
-1. **MUST** Take the file as the review target:
-    - The focus of this review is on the content involved in the diff but the evaluation dimensions need to be based on the file content.
-    - When the diff in the discrepancy report differs from the document content, the diff is only used as a line number reference.
-    - The actual content that needs to be reviewed should be **based on the document content**.
-2. Establish context by **reading relevant files**, files that are **imported/used by** the diff files or are **structurally neighboring** them (e.g., related configuration or test files).
-3. **Ensure the relationship diagram of the diff is complete:**
-    - After establishing the context, analyze the complete context of the difference code to ensure a relatively complete code relationship diagram can be built.
-    - If the content is incomplete, supplement the context and rebuild the relationship diagram.
-4. Read the commit message as the basic understanding of the current change
-5. Determine technology the repository belongs, draw upon your understanding of that technology, provide recommendations on cutting-edge technologies and best practices:
-    - **Consult the workspace introduction** yourself.
-    - Consult cutting-edge industry documentation yourself.
-6. **Execute as many relevant commands as possible to enrich your context.**
-7. **Prioritize Analysis Focus**:
-    - For all collected code, meticulously trace the logic to uncover functional bugs and correctness issues.
-    - Pay attention to the **correctness** of the analytical logic, the **efficiency** of the code, and its **long-term maintainability**.
-    - Concentrate your deepest analysis on the application code (non-test files).
-    - Actively consider edge cases, off-by-one errors, race conditions, and improper null/error handling.
-    - **focusing on major errors**, identify potential bugs, architectural impact, security vulnerabilities, performance bottlenecks, and clarity issues.
-    - focusing on last commit when the same functionality rolling commits occur.
-8. **Maintain skepticism but verify carefully**:
-    - Gather as much context as possible for the code you suspect, raise questions only after **ensuring you have a sufficient understanding** of the business logic.
-    - If doubts persist even after establishing a complete context, lower the severity rating of the issue.
-9. **Strictly** classify the severity according to the content of **file: [severity.instructions.md](./severity.instructions.md)**.
-10. **Further summary report:**
-    - **Tone/Content:** **DO NOT** add comments that:
-      - Tell the user to "check," "confirm," "verify," or "ensure" something.
-      - Explain what the code change does or validate its purpose.
-      - Explain the code to the author (they are assumed to know their own code).
-      - Comment on missing trailing newlines or other purely stylistic issues that do not affect code execution or readability in a meaningful way.
-    - **Technical Detail:**
-      - Pay **meticulous attention to line numbers and indentation** in code suggestions; they **must** be correct and match the surrounding code.
-      - **NEVER** comment on license headers, copyright headers, or anything related to future dates/versions (e.g., "this date is in the future").
-      - **NEVER** comment on the presence or absence of comments in the code.
-    - **Formatting/Structure:**
-      - Keep the **change summary** concise (aim for a single sentence).
-      - Keep **comment bodies concise** and focused on a single issue.
-      - When similar issues occur frequently, please review the code to determine if it meets the change objectives.