@d5render/cli 0.1.57 → 0.1.60

package/bin/d5cli

@@ -51,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
@@ -107,7 +107,7 @@ function installCopilot() {
 //#endregion
 //#region package.json
 var name = "@d5render/cli";
-var version = "0.1.57";
+var version = "0.1.60";
 
 //#endregion
 //#region packages/gitlab/url.ts
@@ -220,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;
@@ -238,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;

package/package.json

@@ -4,7 +4,7 @@
   "license": "MIT",
   "author": "jasirou",
   "main": "./bin/d5cli",
-  "version": "0.1.57",
+  "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.