@dotdotgod/cli 0.2.26 → 0.2.28
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 +11 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -6,7 +6,15 @@ Command-line tools for dotdotgod project memory.
|
|
|
6
6
|
|
|
7
7
|
Use this package when you want to initialize a docs-first project scaffold, validate project-memory docs, build a local graph/cache, search shared documentation locally, expand project references, or ask what should be checked after a file changes.
|
|
8
8
|
|
|
9
|
-
These commands support dotdotgod's project-memory loop with initialization, documentation query, validation, and impact analysis for shells, scripts, CI, and agents
|
|
9
|
+
These commands support dotdotgod's project-memory loop with initialization, documentation query, validation, and impact analysis for shells, scripts, CI, and agents that use the CLI directly.
|
|
10
|
+
|
|
11
|
+
## What Changes
|
|
12
|
+
|
|
13
|
+
- **Repository knowledge becomes navigable memory.** Local multilingual query finds focused documentation evidence and keeps the cache under `.dotdotgod/`.
|
|
14
|
+
- **Project references become actionable context.** `resolve` and `expand` connect explicit `[[...]]` references and high-signal natural-language requests to maintained files; `--with-impact` adds related evidence.
|
|
15
|
+
- **Changes carry their verification neighborhood.** Multi-file graph impact combines structural, traceability, package, and optional semantic evidence while preserving a per-file explanation.
|
|
16
|
+
- **Large repositories reveal natural domains.** `graph communities` groups the maintained project graph to help teams inspect documentation and source boundaries.
|
|
17
|
+
- **Different knowledge shapes can share one workflow.** Editable config templates initialize software or research-oriented memory policies.
|
|
10
18
|
|
|
11
19
|
## Start Here
|
|
12
20
|
|
|
@@ -37,7 +45,7 @@ dotdotgod graph impact . --changed <path> --compact
|
|
|
37
45
|
- `validate` checks the dotdotgod docs/project-memory structure, local links, traceability blocks, config validity, and optional index freshness.
|
|
38
46
|
- `index` builds `.dotdotgod/manifest.json` and compact graph shards from maintained project files.
|
|
39
47
|
- `query` locally embeds shared Markdown with `Xenova/multilingual-e5-small`, incrementally stores vectors under `.dotdotgod/vectors/`, and returns the best-ranked chunk from each relevant Markdown file.
|
|
40
|
-
- `resolve` and `expand` map explicit or high-signal prompt references to project files.
|
|
48
|
+
- `resolve` and `expand` map explicit or high-signal prompt references to project files and can include related impact evidence.
|
|
41
49
|
- `graph impact` ranks likely related specs, tests, docs, commands, and source files for one or more changed paths, with a combined ranking and per-file top five. Non-seed scores use fixed weighted PPR connection `80` plus memory policy `20`. A bounded request-local multilingual vector overlay participates in PPR when the query cache is available; vector preparation failures degrade to structural-only results.
|
|
42
50
|
- `traceability links` checks or repairs generated Markdown traceability-link sections.
|
|
43
51
|
|
|
@@ -58,6 +66,7 @@ dotdotgod query . "plan mode tools"
|
|
|
58
66
|
dotdotgod resolve . PLAN_MODE
|
|
59
67
|
dotdotgod expand . "Update [[PLAN_MODE]] and [[HOOKS]]"
|
|
60
68
|
dotdotgod expand . "PLAN_MODE 수정하자" --fuzzy
|
|
69
|
+
dotdotgod expand . "Update [[PLAN_MODE]]" --with-impact
|
|
61
70
|
dotdotgod traceability links . --check
|
|
62
71
|
dotdotgod traceability links . --write
|
|
63
72
|
dotdotgod graph impact . --changed <path>
|