@getmikk/cli 1.8.2 → 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +34 -14
  2. package/dist/index.js +14722 -12187
  3. package/dist/index.js.map +4 -4
  4. package/package.json +11 -11
package/README.md CHANGED
@@ -39,6 +39,30 @@ mikk init
39
39
  # 8. Generate claude.md and AGENTS.md
40
40
  ```
41
41
 
42
+ ---
43
+
44
+ ## Professional CLI snapshot
45
+
46
+ `mikk init --force` now emits a structured **Project snapshot** panel (files, nodes, edges, functions, exports, modules) followed by the top module coordinates and a **Context & schema files** panel so you can review the analysis without hunting through logs.
47
+
48
+ ```
49
+ ┌─ Project snapshot ─────────────────────────────────────────────────────────┐
50
+ │ Files 181 │
51
+ │ Graph nodes 3716 │
52
+ │ Graph edges 3611 │
53
+ │ Functions 213 │
54
+ │ Exported APIs 79 │
55
+ │ Modules 1 │
56
+ └────────────────────────────────────────────────────────────────────────────┘
57
+ █ Graph density 0.97 edges/node
58
+ ```
59
+
60
+ The human-friendly digest makes it easy to confirm the graph scale before drilling into modules, contexts, or constraints.
61
+
62
+ ## Benchmark note (GitNexus)
63
+
64
+ We attempted to benchmark against GitNexus (`npx --yes --package gitnexus gitnexus analyze`) but the CLI install is blocked inside this sandbox: npm raises `EACCES` while fetching `gitnexus` (error: `FetchError: request to https://registry.npmjs.org/gitnexus failed`). Once the platform permissions allow installing npm packages you can rerun the command to capture the repo metrics.
65
+
42
66
  ---
43
67
 
44
68
  ## Commands
@@ -137,20 +161,16 @@ mikk contract validate --strict
137
161
  run: mikk contract validate --boundaries-only --strict
138
162
  ```
139
163
 
140
- #### `mikk contract generate`
141
-
142
- Regenerate the `mikk.json` skeleton from the current codebase. Useful after major refactoring.
143
-
144
- ```bash
145
- mikk contract generate
146
- ```
164
+ #### Contract regeneration
147
165
 
148
- #### `mikk contract update`
166
+ Mikk regenerates `mikk.json` / `mikk.lock.json` as part of:
149
167
 
150
- Update the lock file to match the current codebase state.
168
+ - `mikk init` (full project scan + artifacts generation)
169
+ - `mikk analyze` (re-analyze + update generated artifacts)
151
170
 
152
171
  ```bash
153
- mikk contract update
172
+ mikk init
173
+ mikk analyze
154
174
  ```
155
175
 
156
176
  #### `mikk contract show-boundaries`
@@ -299,19 +319,19 @@ Regenerate the diagram for a specific module.
299
319
  mikk visualize module auth
300
320
  ```
301
321
 
302
- #### `mikk visualize impact`
322
+ #### `mikk context impact`
303
323
 
304
- Generate an impact diagram based on current file changes (files that differ from the lock file).
324
+ Analyze what breaks if a specific file changes (and includes an AI-context-focused impacted view).
305
325
 
306
326
  ```bash
307
- mikk visualize impact
327
+ mikk context impact src/auth/login.ts
308
328
  ```
309
329
 
310
330
  ---
311
331
 
312
332
  ### `mikk mcp` — MCP Server for AI Assistants
313
333
 
314
- Connect your project architecture to Claude Desktop, Cursor, VS Code, or any MCP-compatible AI tool. The MCP server exposes 15 tools and 3 resources for your assistant, all powered by the Mikk lock file.
334
+ Connect your project architecture to Claude Desktop, Cursor, VS Code, or any MCP-compatible AI tool. The MCP server exposes 22 tools and 3 resources for your assistant, all powered by the Mikk lock file.
315
335
 
316
336
  #### `mikk mcp` (default: start server)
317
337