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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ant-design/cli",
-  "version": "6.3.5-beta.0",
+  "version": "6.3.5",
   "description": "CLI tool for querying antd knowledge and analyzing antd usage in projects",
   "type": "module",
   "bin": {
@@ -43,12 +43,14 @@
     "access": "public"
   },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.27.1",
-    "commander": "~13.1.0",
     "oxc-parser": "^0.121.0"
   },
   "devDependencies": {
+    "@modelcontextprotocol/sdk": "^1.27.1",
     "@types/node": "^25.5.0",
+    "@vitest/coverage-v8": "^3.2.4",
+    "commander": "~13.1.0",
+    "envinfo": "^7.21.0",
     "gray-matter": "^4.0.3",
     "tsup": "^8.4.0",
     "tsx": "^4.19.0",

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:
 
 ```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,7 +190,7 @@ antd bug --title "DatePicker crashes when selecting date" \
   --submit
 ```
 
-### 9. Auto-reporting CLI issues
+### 10. 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`.**
 
@@ -205,7 +229,7 @@ antd bug-cli --title "antd info Button returns wrong props for v5.12.0" \
 
 **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.
 
-### 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 +262,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.
+6. **Report antd bugs** — First run `antd env` to capture the full environment, then use `antd bug` to report. 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.