@ant-design/cli 6.4.2 → 6.4.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ant-design/cli",
-  "version": "6.4.2",
+  "version": "6.4.3",
   "description": "CLI tool for querying antd knowledge and analyzing antd usage in projects",
   "type": "module",
   "bin": {
@@ -48,11 +48,17 @@
     "ip-address": "^10.1.1"
   },
   "dependencies": {
-    "oxc-parser": "^0.130.0"
+    "fast-glob": "^3.3.3",
+    "fast-levenshtein": "^3.0.0",
+    "oxc-parser": "^0.130.0",
+    "semver": "^7.8.0",
+    "string-width": "^8.2.1"
   },
   "devDependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
+    "@types/fast-levenshtein": "^0.0.4",
     "@types/node": "^25.5.0",
+    "@types/semver": "^7.7.1",
     "@vitest/coverage-v8": "^4.1.2",
     "commander": "^14.0.3",
     "conf": "^15.1.0",

package/skills/antd/SKILL.md

@@ -15,7 +15,7 @@ allowed-tools:
 
 # Ant Design CLI
 
-You have access to `@ant-design/cli` — a local CLI tool with bundled antd metadata for v3/v4/v5/v6. Use it to query component knowledge, analyze projects, and guide migrations. All data is offline, no network needed.
+You have access to `@ant-design/cli` — a local CLI tool with bundled antd metadata for v4/v5/v6 (plus migration guides for v3 → v4, v4 → v5, v5 → v6). Use it to query component knowledge, analyze projects, and guide migrations. All data is offline, no network needed.
 
 ## Setup
 
@@ -93,6 +93,9 @@ antd migrate 4 5 --format json    # v4 → v5
 # Check migration for a specific component
 antd migrate 4 5 --component Select --format json
 
+# Generate agent-friendly auto-migration prompt (does not modify files)
+antd migrate 4 5 --apply ./src --format json
+
 # See what changed between two versions
 antd changelog 4.24.0 5.0.0 --format json
 
@@ -239,15 +242,16 @@ This provides 7 tools (`antd_list`, `antd_info`, `antd_doc`, `antd_demo`, `antd_
 
 | Flag | Purpose |
 |---|---|
-| `--format json` | Structured output — always use this |
+| `--format <format>` | Output format: `json`, `text`, or `markdown` (agents should prefer `json`) |
 | `--version <v>` | Target a specific antd version (e.g. `5.20.0`) |
 | `--lang zh` | Chinese output (default: `en`) |
 | `--detail` | Include extra fields (description, since, deprecated, FAQ) |
+| `-V, --cli-version` | Print CLI version and exit |
 
 ## Key Rules
 
 1. **Always query before writing** — Don't guess antd APIs from memory. Run `antd info` first.
-2. **Match the user's version** — If the project uses antd 3.x or 4.x, pass `--version 3.26.0` or `--version 4.24.0`. The CLI auto-detects from `node_modules` if no flag is given.
+2. **Match the user's version** — Knowledge queries (`list/info/doc/demo/token/semantic/changelog`) support antd v4+. If the project uses antd 4.x/5.x/6.x, pass `--version 4.24.0` / `5.24.0` / `6.x`. For antd v3 projects, use `antd migrate 3 4` first.
 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.