@ant-design/cli 6.3.5-beta.0 → 6.3.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ant-design/cli",
-  "version": "6.3.5-beta.0",
+  "version": "6.3.6",
   "description": "CLI tool for querying antd knowledge and analyzing antd usage in projects",
   "type": "module",
   "bin": {
@@ -24,7 +24,7 @@
     "postpack": "tsx scripts/compress-data.ts --undo"
   },
   "engines": {
-    "node": ">=18.0.0"
+    "node": ">=20.0.0"
   },
   "keywords": [
     "ant-design",
@@ -43,16 +43,18 @@
     "access": "public"
   },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.27.1",
-    "commander": "~13.1.0",
-    "oxc-parser": "^0.121.0"
+    "oxc-parser": "^0.123.0"
   },
   "devDependencies": {
+    "@modelcontextprotocol/sdk": "^1.29.0",
     "@types/node": "^25.5.0",
+    "@vitest/coverage-v8": "^4.1.2",
+    "commander": "^14.0.3",
+    "envinfo": "^7.21.0",
     "gray-matter": "^4.0.3",
     "tsup": "^8.4.0",
     "tsx": "^4.19.0",
-    "typescript": "^5.7.0",
-    "vitest": "^3.0.0"
+    "typescript": "^5.9.3",
+    "vitest": "^4.1.2"
   }
 }

package/skills/antd/SKILL.md

@@ -66,6 +66,9 @@ antd doc Table --lang zh            # Chinese docs
 When code isn't working as expected or the user reports an antd bug:
 
 ```bash
+# Collect full environment snapshot (system, deps, browsers, build tools)
+antd env --format json
+
 # Check if the prop exists for the user's antd version
 antd info Select --version 5.12.0 --format json
 
@@ -76,7 +79,7 @@ antd lint ./src/components/MyForm.tsx --format json
 antd doctor --format json
 ```
 
-**Workflow:** `antd doctor` → check environment → `antd info --version X` → verify API against the user's exact version → `antd lint` → find deprecated or incorrect usage.
+**Workflow:** `antd env` → capture full environment → `antd doctor` → check configuration → `antd info --version X` → verify API against the user's exact version → `antd lint` → find deprecated or incorrect usage.
 
 ### 4. Migrating between versions
 
@@ -142,11 +145,32 @@ antd list --format json
 antd list --version 5.0.0 --format json
 ```
 
-### 8. Reporting antd bugs
+### 8. Collecting environment info
+
+When you need to understand the project's antd setup, or prepare info for a bug report:
+
+```bash
+# Full environment snapshot (text — paste into GitHub Issues)
+antd env
+
+# Structured JSON for programmatic use
+antd env --format json
+
+# Scan a specific project directory
+antd env ./my-project --format json
+```
+
+Collects: OS, Node, package managers (npm/pnpm/yarn/bun/utoo), npm registry, browsers, core deps (antd/react/dayjs), all `@ant-design/*` and `rc-*` packages, and build tools (umi/vite/webpack/typescript/etc.).
+
+### 9. Reporting antd bugs
 
-When you encounter a confirmed antd component bug that can't be resolved locally:
+When the user asks you to report an antd bug:
 
 ```bash
+# Step 0: Collect environment info for reference (optional — antd bug already embeds basic env)
+# Use the output to cross-check versions or attach extra details to the bug report
+antd env --format json
+
 # Step 1: Preview for user review
 antd bug --title "DatePicker crashes when selecting date" \
   --reproduction "https://codesandbox.io/s/xxx" \
@@ -166,23 +190,12 @@ antd bug --title "DatePicker crashes when selecting date" \
   --submit
 ```
 
-### 9. Auto-reporting CLI issues
-
-**IMPORTANT: Whenever you use any `antd` CLI command and notice something wrong, you should proactively initiate a bug report using `antd bug-cli`.**
-
-Trigger conditions — report a CLI bug when you observe any of these:
-- A command **crashes or exits with an unexpected error**
-- A command **returns clearly incorrect data** (e.g. `antd info Button` shows wrong props, missing props, or props from the wrong version)
-- A command's **output doesn't match its documented behavior** (e.g. `--format json` returns non-JSON, `--version X` is ignored)
-- A command **returns empty or missing data** when it shouldn't (e.g. `antd demo Button` returns no demos, `antd token Button` returns no tokens for v5+)
-- **Inconsistencies between commands** (e.g. `antd list` shows a component but `antd info` says it doesn't exist)
+### 10. Reporting CLI issues
 
-**Workflow:**
-1. You notice something wrong while using the CLI
-2. Gather evidence: the exact command you ran, what was returned, and what you expected
-3. Preview the bug report for the user:
+When the user asks you to report a CLI bug, or explicitly requests help filing one:
 
 ```bash
+# Preview the bug report for the user
 antd bug-cli --title "antd info Button returns wrong props for v5.12.0" \
   --description "When querying Button props for version 5.12.0, the output includes props that don't exist in that version" \
   --steps "1. Run: antd info Button --version 5.12.0 --format json" \
@@ -191,8 +204,7 @@ antd bug-cli --title "antd info Button returns wrong props for v5.12.0" \
   --format json
 ```
 
-4. Show the report to the user: "I noticed an issue with the CLI while working. Here's a bug report — shall I submit it?"
-5. Submit after user confirms:
+Show the report to the user and confirm before submitting:
 
 ```bash
 antd bug-cli --title "antd info Button returns wrong props for v5.12.0" \
@@ -203,9 +215,9 @@ antd bug-cli --title "antd info Button returns wrong props for v5.12.0" \
   --submit
 ```
 
-**Key principle:** You are a quality feedback loop for the CLI. Don't silently work around CLI issues — report them so they get fixed. Always confirm with the user before submitting.
+**Opt-out:** If the environment variable `ANTD_NO_AUTO_REPORT=1` is set, skip all bug-reporting suggestions entirely — do not suggest `antd bug` or `antd bug-cli` unless the user directly asks.
 
-### 10. Using as MCP server
+### 11. Using as MCP server
 
 If working in an IDE that supports MCP (Claude Desktop, Cursor, etc.), the CLI can also run as an MCP server, exposing all knowledge-query tools directly:
 
@@ -238,5 +250,5 @@ This provides 7 tools (`antd_list`, `antd_info`, `antd_doc`, `antd_demo`, `antd_
 3. **Use `--format json`** — Every command supports it. Parse the JSON output rather than regex-matching text output.
 4. **Check before suggesting migration** — Run `antd changelog <v1> <v2>` and `antd migrate` before advising on version upgrades.
 5. **Lint after changes** — After writing or modifying antd code, run `antd lint` on the changed files to catch deprecated or problematic usage.
-6. **Report antd bugs** — When you encounter an antd component bug, use `antd bug` to report it. Always preview first, get user confirmation, then submit.
-7. **Auto-report CLI issues** — If any `antd` command crashes, returns wrong data, or behaves inconsistently, proactively use `antd bug-cli` to report it. You are the quality feedback loop for the CLI — don't silently work around issues.
+6. **Report antd bugs** — When the user asks to report an antd bug, use `antd bug`. Always preview first, get user confirmation, then submit.
+7. **Report CLI issues** — When the user asks about a CLI problem, use `antd bug-cli` to help them file a report. Always preview first, get user confirmation, then submit.