depwire-cli 0.2.5 → 0.3.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.
package/README.md CHANGED
@@ -8,6 +8,7 @@ Depwire analyzes codebases to build a cross-reference graph showing how every fi
8
8
 
9
9
  - 🎨 **Beautiful arc diagram visualization** — Interactive Harrison Bible-style graphic
10
10
  - 🤖 **MCP server for AI tools** — Cursor, Claude Desktop get full dependency context
11
+ - 📄 **Auto-generated documentation** — Architecture, conventions, dependencies, and onboarding docs generated from your dependency graph
11
12
  - 🔍 **Impact analysis** — "What breaks if I rename this function?" answered precisely
12
13
  - 👀 **Live updates** — Graph stays current as you edit code
13
14
  - 🌍 **Multi-language** — TypeScript, JavaScript, Python, and Go
@@ -36,8 +37,8 @@ Depwire fixes this by giving AI tools a complete dependency graph of your codeba
36
37
  - **Live graph, always current** — edit a file and the dependency map updates in real-time. No re-indexing, no waiting.
37
38
  - **Works locally, stays private** — zero cloud accounts, zero data leaving your machine. Just `npm install` and go.
38
39
 
39
- ### 10 MCP Tools, Not Just Visualization
40
- Depwire isn't just a pretty graph. It's a full context engine with 10 tools that AI assistants call autonomously — architecture summaries, dependency tracing, symbol search, file context, and more. The AI decides which tool to use based on your question.
40
+ ### 12 MCP Tools, Not Just Visualization
41
+ Depwire isn't just a pretty graph. It's a full context engine with 12 tools that AI assistants call autonomously — architecture summaries, dependency tracing, symbol search, file context, and more. The AI decides which tool to use based on your question.
41
42
 
42
43
  ## Installation
43
44
 
@@ -72,6 +73,9 @@ npx depwire-cli parse ./my-project --verbose
72
73
  # Export with pretty-printed JSON and statistics
73
74
  npx depwire-cli parse ./my-project --pretty --stats
74
75
 
76
+ # Generate codebase documentation
77
+ npx depwire-cli docs ./my-project --verbose --stats
78
+
75
79
  # Custom output file
76
80
  npx depwire-cli parse ./my-project -o my-graph.json
77
81
  ```
@@ -116,6 +120,8 @@ Settings → Features → Experimental → Enable MCP → Add Server:
116
120
  | `list_files` | List all files with stats |
117
121
  | `get_symbol_info` | Look up any symbol's details |
118
122
  | `visualize_graph` | Generate interactive arc diagram visualization |
123
+ | `get_project_docs` | Retrieve auto-generated codebase documentation |
124
+ | `update_project_docs` | Regenerate documentation on demand |
119
125
 
120
126
  ## Supported Languages
121
127
 
@@ -225,6 +231,54 @@ depwire mcp
225
231
  depwire mcp /path/to/project
226
232
  ```
227
233
 
234
+ ### `depwire docs <directory>`
235
+
236
+ Generate comprehensive codebase documentation from your dependency graph.
237
+
238
+ **Options:**
239
+ - `--output <path>` — Output directory (default: `.depwire/` inside project)
240
+ - `--format <type>` — Output format: `markdown` or `json` (default: `markdown`)
241
+ - `--include <docs...>` — Comma-separated list of docs to generate (default: `all`)
242
+ - Values: `architecture`, `conventions`, `dependencies`, `onboarding`, `all`
243
+ - `--update` — Regenerate existing documentation
244
+ - `--only <docs...>` — Used with `--update`, regenerate only specific docs
245
+ - `--verbose` — Show generation progress
246
+ - `--stats` — Show generation statistics
247
+ - `--gitignore` — Add `.depwire/` to `.gitignore` automatically
248
+ - `--no-gitignore` — Don't modify `.gitignore`
249
+
250
+ **Examples:**
251
+ ```bash
252
+ # Generate all docs (outputs to .depwire/ by default)
253
+ depwire docs ./my-project
254
+
255
+ # Show generation progress and stats
256
+ depwire docs ./my-project --verbose --stats
257
+
258
+ # Regenerate existing docs
259
+ depwire docs ./my-project --update
260
+
261
+ # Generate specific docs only
262
+ depwire docs ./my-project --include architecture,dependencies
263
+
264
+ # Custom output directory
265
+ depwire docs ./my-project --output ./docs
266
+
267
+ # Regenerate only conventions doc
268
+ depwire docs ./my-project --update --only conventions
269
+ ```
270
+
271
+ **Generated Documents:**
272
+
273
+ | Document | What It Contains |
274
+ |----------|------------------|
275
+ | `ARCHITECTURE.md` | Module structure, entry points, hub files, layer analysis, circular dependencies |
276
+ | `CONVENTIONS.md` | Naming patterns, import/export style, detected design patterns |
277
+ | `DEPENDENCIES.md` | Module dependency matrix, high-impact symbols, longest dependency chains |
278
+ | `ONBOARDING.md` | Reading order (Foundation/Core/Entry Points), module map, key concepts, high-impact file warnings |
279
+
280
+ Documents are stored in `.depwire/` with `metadata.json` tracking generation timestamps for staleness detection.
281
+
228
282
  ### Error Handling
229
283
 
230
284
  Depwire gracefully handles parse errors: