claude-db 0.11.0 → 0.12.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/CHANGELOG.md +63 -0
- package/README.md +44 -81
- package/dist/catchup/gather.d.ts +1 -0
- package/dist/catchup/gather.js +9 -2
- package/dist/catchup/git-state.d.ts +2 -0
- package/dist/catchup/git-state.js +3 -0
- package/dist/catchup/render.js +8 -0
- package/dist/cli/commands/graph.js +104 -80
- package/dist/cli/commands/languages.d.ts +1 -0
- package/dist/cli/commands/languages.js +22 -0
- package/dist/cli/files.d.ts +2 -0
- package/dist/cli/files.js +15 -1
- package/dist/cli/index.js +4 -0
- package/dist/cli/install.js +4 -3
- package/dist/cli/skills.js +6 -1
- package/dist/cli/usage.js +3 -1
- package/dist/facts/distill.d.ts +0 -2
- package/dist/facts/distill.js +4 -26
- package/dist/facts/handoff.js +11 -1
- package/dist/facts/known.d.ts +4 -0
- package/dist/facts/known.js +38 -0
- package/dist/facts/ops.d.ts +1 -1
- package/dist/facts/ops.js +4 -2
- package/dist/facts/start.js +5 -1
- package/dist/graph/ast.d.ts +4 -0
- package/dist/graph/ast.js +11 -0
- package/dist/graph/grammars.d.ts +14 -0
- package/dist/graph/grammars.js +58 -0
- package/dist/graph/index.d.ts +2 -2
- package/dist/graph/index.js +2 -2
- package/dist/graph/languages/basic.js +5 -1
- package/dist/graph/languages/ecmascript.js +7 -0
- package/dist/graph/languages/go.js +0 -1
- package/dist/graph/languages/index.d.ts +1 -1
- package/dist/graph/languages/index.js +34 -9
- package/dist/graph/languages/java.d.ts +2 -0
- package/dist/graph/languages/java.js +38 -0
- package/dist/graph/languages/kotlin.d.ts +2 -0
- package/dist/graph/languages/kotlin.js +19 -0
- package/dist/graph/languages/python.js +10 -2
- package/dist/graph/languages/rules.d.ts +11 -0
- package/dist/graph/languages/rust.js +2 -1
- package/dist/graph/modules/binding.d.ts +61 -0
- package/dist/graph/modules/binding.js +43 -0
- package/dist/graph/modules/ecmascript/bind.d.ts +4 -0
- package/dist/graph/modules/ecmascript/bind.js +17 -0
- package/dist/graph/modules/ecmascript/contexts.d.ts +6 -0
- package/dist/graph/modules/ecmascript/contexts.js +86 -0
- package/dist/graph/modules/ecmascript/exports.d.ts +9 -0
- package/dist/graph/modules/ecmascript/exports.js +91 -0
- package/dist/graph/modules/ecmascript/imports.d.ts +4 -0
- package/dist/graph/modules/ecmascript/imports.js +73 -0
- package/dist/graph/modules/ecmascript/package-resolver.d.ts +4 -0
- package/dist/graph/modules/ecmascript/package-resolver.js +73 -0
- package/dist/graph/modules/ecmascript/resolver.d.ts +2 -0
- package/dist/graph/modules/ecmascript/resolver.js +22 -0
- package/dist/graph/modules/ecmascript/specifiers.d.ts +3 -0
- package/dist/graph/modules/ecmascript/specifiers.js +15 -0
- package/dist/graph/modules/ecmascript/system.d.ts +2 -0
- package/dist/graph/modules/ecmascript/system.js +18 -0
- package/dist/graph/modules/ecmascript/workspace-resolver.d.ts +5 -0
- package/dist/graph/modules/ecmascript/workspace-resolver.js +38 -0
- package/dist/graph/modules/go/grammar.d.ts +2 -0
- package/dist/graph/modules/go/grammar.js +54 -0
- package/dist/graph/modules/go/imports.d.ts +4 -0
- package/dist/graph/modules/go/imports.js +32 -0
- package/dist/graph/modules/go/resolver.d.ts +2 -0
- package/dist/graph/modules/go/resolver.js +54 -0
- package/dist/graph/modules/go/system.d.ts +2 -0
- package/dist/graph/modules/go/system.js +16 -0
- package/dist/graph/modules/java/declarations.d.ts +9 -0
- package/dist/graph/modules/java/declarations.js +108 -0
- package/dist/graph/modules/java/grammar.d.ts +2 -0
- package/dist/graph/modules/java/grammar.js +135 -0
- package/dist/graph/modules/java/imports.d.ts +4 -0
- package/dist/graph/modules/java/imports.js +13 -0
- package/dist/graph/modules/java/receivers.d.ts +3 -0
- package/dist/graph/modules/java/receivers.js +139 -0
- package/dist/graph/modules/java/system.d.ts +1 -0
- package/dist/graph/modules/java/system.js +13 -0
- package/dist/graph/modules/jvm/linking.d.ts +20 -0
- package/dist/graph/modules/jvm/linking.js +64 -0
- package/dist/graph/modules/jvm/packages.d.ts +5 -0
- package/dist/graph/modules/jvm/packages.js +58 -0
- package/dist/graph/modules/jvm/receivers.d.ts +44 -0
- package/dist/graph/modules/jvm/receivers.js +77 -0
- package/dist/graph/modules/jvm/system.d.ts +18 -0
- package/dist/graph/modules/jvm/system.js +29 -0
- package/dist/graph/modules/jvm/types.d.ts +3 -0
- package/dist/graph/modules/jvm/types.js +11 -0
- package/dist/graph/modules/kotlin/declarations.d.ts +8 -0
- package/dist/graph/modules/kotlin/declarations.js +69 -0
- package/dist/graph/modules/kotlin/grammar.d.ts +2 -0
- package/dist/graph/modules/kotlin/grammar.js +78 -0
- package/dist/graph/modules/kotlin/imports.d.ts +4 -0
- package/dist/graph/modules/kotlin/imports.js +25 -0
- package/dist/graph/modules/kotlin/receivers.d.ts +3 -0
- package/dist/graph/modules/kotlin/receivers.js +105 -0
- package/dist/graph/modules/kotlin/references.d.ts +8 -0
- package/dist/graph/modules/kotlin/references.js +69 -0
- package/dist/graph/modules/kotlin/system.d.ts +1 -0
- package/dist/graph/modules/kotlin/system.js +15 -0
- package/dist/graph/modules/members.d.ts +17 -0
- package/dist/graph/modules/members.js +30 -0
- package/dist/graph/modules/module-index.d.ts +9 -0
- package/dist/graph/modules/module-index.js +62 -0
- package/dist/graph/modules/names.d.ts +2 -0
- package/dist/graph/modules/names.js +3 -0
- package/dist/graph/modules/python/grammar.d.ts +2 -0
- package/dist/graph/modules/python/grammar.js +100 -0
- package/dist/graph/modules/python/imports.d.ts +3 -0
- package/dist/graph/modules/python/imports.js +72 -0
- package/dist/graph/modules/python/resolver.d.ts +2 -0
- package/dist/graph/modules/python/resolver.js +78 -0
- package/dist/graph/modules/python/system.d.ts +2 -0
- package/dist/graph/modules/python/system.js +16 -0
- package/dist/graph/modules/rebind.d.ts +8 -0
- package/dist/graph/modules/rebind.js +51 -0
- package/dist/graph/modules/registry.d.ts +5 -0
- package/dist/graph/modules/registry.js +47 -0
- package/dist/graph/modules/rust/grammar.d.ts +2 -0
- package/dist/graph/modules/rust/grammar.js +94 -0
- package/dist/graph/modules/rust/imports.d.ts +3 -0
- package/dist/graph/modules/rust/imports.js +90 -0
- package/dist/graph/modules/rust/resolver.d.ts +3 -0
- package/dist/graph/modules/rust/resolver.js +153 -0
- package/dist/graph/modules/rust/system.d.ts +2 -0
- package/dist/graph/modules/rust/system.js +16 -0
- package/dist/graph/modules/shadowing.d.ts +17 -0
- package/dist/graph/modules/shadowing.js +65 -0
- package/dist/graph/modules/system.d.ts +39 -0
- package/dist/graph/modules/system.js +1 -0
- package/dist/graph/modules/uses.d.ts +14 -0
- package/dist/graph/modules/uses.js +62 -0
- package/dist/graph/parser.d.ts +9 -11
- package/dist/graph/parser.js +5 -4
- package/dist/graph/query/answer.d.ts +15 -0
- package/dist/graph/query/answer.js +22 -0
- package/dist/graph/query/format.d.ts +8 -1
- package/dist/graph/query/format.js +103 -30
- package/dist/graph/query/groups.d.ts +14 -0
- package/dist/graph/query/groups.js +51 -0
- package/dist/graph/query/index.d.ts +2 -1
- package/dist/graph/query/index.js +2 -1
- package/dist/graph/query/lookup.d.ts +2 -0
- package/dist/graph/query/lookup.js +19 -2
- package/dist/graph/query/refresh.js +17 -18
- package/dist/graph/query/stale.d.ts +2 -0
- package/dist/graph/query/stale.js +39 -0
- package/dist/graph/query/text.d.ts +12 -0
- package/dist/graph/query/text.js +26 -0
- package/dist/graph/scan/binder.d.ts +13 -0
- package/dist/graph/scan/binder.js +210 -0
- package/dist/graph/scan/cache.d.ts +11 -0
- package/dist/graph/scan/cache.js +140 -0
- package/dist/graph/scan/extract.d.ts +4 -17
- package/dist/graph/scan/extract.js +105 -83
- package/dist/graph/scan/files.d.ts +3 -9
- package/dist/graph/scan/files.js +3 -2
- package/dist/graph/scan/index.d.ts +8 -3
- package/dist/graph/scan/index.js +96 -36
- package/dist/graph/scan/job.d.ts +1 -0
- package/dist/graph/scan/job.js +1 -0
- package/dist/graph/scan/persist.d.ts +3 -0
- package/dist/graph/scan/persist.js +22 -0
- package/dist/graph/scan/receivers.d.ts +21 -0
- package/dist/graph/scan/receivers.js +87 -0
- package/dist/graph/scan/resolve.d.ts +8 -2
- package/dist/graph/scan/resolve.js +50 -56
- package/dist/graph/scan/spans.d.ts +13 -0
- package/dist/graph/scan/spans.js +42 -0
- package/dist/graph/symbols.d.ts +10 -0
- package/dist/graph/symbols.js +30 -0
- package/dist/graph/types.d.ts +56 -0
- package/dist/graph/types.js +1 -0
- package/dist/hooks/background.js +1 -16
- package/dist/hooks/detached.d.ts +3 -0
- package/dist/hooks/detached.js +16 -0
- package/dist/hooks/graph-refresh.d.ts +1 -0
- package/dist/hooks/graph-refresh.js +9 -0
- package/dist/hooks/prefer-usages.js +53 -12
- package/dist/hooks/session-start.js +8 -8
- package/dist/mcp/tools/usages.js +40 -31
- package/dist/types.d.ts +1 -1
- package/dist/usages/find.js +1 -0
- package/docs/how-it-works.md +10 -8
- package/docs/setup-guide.md +47 -299
- package/package.json +17 -6
- package/skills/catchup/SKILL.md +2 -0
- package/skills/handoff/SKILL.md +23 -7
package/dist/mcp/tools/usages.js
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
import { z } from 'zod';
|
|
2
2
|
import { findUsages as textUsages, formatUsages, repoRootFor } from '../../usages/index.js';
|
|
3
|
-
import {
|
|
3
|
+
import { NO_GRAPH, NO_GRAPH_FOR_PATH, answerQuery, formatGraph, hasGraph, suggestFor, } from '../../graph/index.js';
|
|
4
4
|
import { resolveProject } from '../../util/project.js';
|
|
5
5
|
export function register(server, ctx) {
|
|
6
6
|
server.tool('find_usages', 'USE THIS INSTEAD OF grep/rg WHENEVER THE THING YOU ARE LOOKING UP IS A CODE ' +
|
|
@@ -9,16 +9,16 @@ export function register(server, ctx) {
|
|
|
9
9
|
'grep cannot tell a call from an import from an inherit and will not show ' +
|
|
10
10
|
'you the blast radius. Reach for grep only for what is genuinely text: ' +
|
|
11
11
|
'plain prose, comments, log output, string literals, multi-pattern regex, ' +
|
|
12
|
-
'or the scoping flags this tool does not expose. Modes: "usages"
|
|
13
|
-
'references the symbol with the relation on each line,
|
|
14
|
-
'
|
|
15
|
-
'
|
|
16
|
-
'
|
|
17
|
-
'
|
|
18
|
-
'
|
|
19
|
-
'
|
|
20
|
-
'
|
|
21
|
-
'
|
|
12
|
+
'or the scoping flags this tool does not expose. Modes: "usages" (default) ' +
|
|
13
|
+
'lists what references the symbol, with the relation on each line, then the ' +
|
|
14
|
+
'grep lines the graph could not link; "explain" adds what the symbol reaches, ' +
|
|
15
|
+
'"path" traces how two symbols connect (pass the second as `target`), and ' +
|
|
16
|
+
'"text" is a plain live `git grep`. Graph modes re-parse anything that ' +
|
|
17
|
+
'changed before replying, and answer from text until `claude-db scan` has ' +
|
|
18
|
+
'run. Every edge is tagged EXTRACTED (read literally from the syntax) or ' +
|
|
19
|
+
'INFERRED (matched by name across files, with a score). A miss suggests near ' +
|
|
20
|
+
'names, so a half-remembered symbol is still worth asking about. Use `search` ' +
|
|
21
|
+
'instead for "why is this the way it is" (history).', {
|
|
22
22
|
symbol: z
|
|
23
23
|
.string()
|
|
24
24
|
.min(1)
|
|
@@ -26,9 +26,9 @@ export function register(server, ctx) {
|
|
|
26
26
|
.describe('Exact name to search for, e.g. "useAuth" or "CartButton"'),
|
|
27
27
|
mode: z
|
|
28
28
|
.enum(['text', 'usages', 'explain', 'path'])
|
|
29
|
-
.default('
|
|
30
|
-
.describe('How to answer. "
|
|
31
|
-
'
|
|
29
|
+
.default('usages')
|
|
30
|
+
.describe('How to answer. "usages" (default) uses the code graph plus grep; "text" ' +
|
|
31
|
+
'greps live only'),
|
|
32
32
|
target: z.string().optional().describe('The second symbol, for mode "path" only'),
|
|
33
33
|
path: z
|
|
34
34
|
.string()
|
|
@@ -58,23 +58,32 @@ export function register(server, ctx) {
|
|
|
58
58
|
.describe('Cap on matching lines returned; the result says how many more exist'),
|
|
59
59
|
}, (args) => find_usages(ctx, args));
|
|
60
60
|
}
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
61
|
+
const reply = (text) => ({ content: [{ type: 'text', text }] });
|
|
62
|
+
async function textAnswer(ctx, args) {
|
|
63
|
+
const { symbol, regex, context, limit, path } = args;
|
|
64
|
+
const result = textUsages({ symbol, regex, context, limit, ...(path ? { path } : {}) });
|
|
65
|
+
const missed = result.matches.length === 0
|
|
66
|
+
? await suggestFor(ctx.store, resolveProject(undefined), symbol)
|
|
67
|
+
: [];
|
|
68
|
+
return formatUsages(result, missed);
|
|
69
|
+
}
|
|
70
|
+
async function find_usages(ctx, args) {
|
|
71
|
+
if (args.mode === 'text')
|
|
72
|
+
return reply(await textAnswer(ctx, args));
|
|
70
73
|
const project = resolveProject(undefined);
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
74
|
+
if (!(await hasGraph(ctx.store, project))) {
|
|
75
|
+
if (args.mode === 'path')
|
|
76
|
+
return reply(NO_GRAPH_FOR_PATH);
|
|
77
|
+
return reply(`${NO_GRAPH}\n${await textAnswer(ctx, args)}`);
|
|
78
|
+
}
|
|
79
|
+
const root = repoRootFor(args.path ?? process.cwd());
|
|
80
|
+
const { mode, symbol, target, limit } = args;
|
|
81
|
+
const answer = await answerQuery({
|
|
82
|
+
store: ctx.store,
|
|
83
|
+
root,
|
|
84
|
+
project,
|
|
85
|
+
query: { mode, symbol, ...(target ? { target } : {}), limit },
|
|
86
|
+
refresh: true,
|
|
77
87
|
});
|
|
78
|
-
answer
|
|
79
|
-
return { content: [{ type: 'text', text: formatGraph(answer, root) }] };
|
|
88
|
+
return reply(formatGraph(answer, root));
|
|
80
89
|
}
|
package/dist/types.d.ts
CHANGED
|
@@ -68,7 +68,7 @@ export interface TimelineQuery {
|
|
|
68
68
|
after: number;
|
|
69
69
|
}
|
|
70
70
|
export type SymbolKind = 'function' | 'class' | 'interface' | 'type' | 'enum' | 'const' | 'method';
|
|
71
|
-
export type EdgeRelation = 'calls' | 'imports' | 'extends' | 'implements' | 'references' | 'defines';
|
|
71
|
+
export type EdgeRelation = 'calls' | 'imports' | 'extends' | 'implements' | 'references' | 'defines' | 'aliases';
|
|
72
72
|
export type EdgeConfidence = 'EXTRACTED' | 'INFERRED';
|
|
73
73
|
export interface CodeSymbol {
|
|
74
74
|
id: string;
|
package/dist/usages/find.js
CHANGED
package/docs/how-it-works.md
CHANGED
|
@@ -172,12 +172,15 @@ re-parses files whose contents changed.
|
|
|
172
172
|
|
|
173
173
|
`find_usages` then answers in four modes, over MCP as well as the CLI:
|
|
174
174
|
|
|
175
|
-
| mode
|
|
176
|
-
|
|
|
177
|
-
| `
|
|
178
|
-
| `
|
|
179
|
-
| `
|
|
180
|
-
| `
|
|
175
|
+
| mode | answers |
|
|
176
|
+
| ------------------ | ----------------------------------------------------------- |
|
|
177
|
+
| `usages` (default) | what references this symbol, with the relation on each line |
|
|
178
|
+
| `explain` | that, plus what the symbol itself reaches |
|
|
179
|
+
| `path` | how two symbols connect |
|
|
180
|
+
| `text` | live `git grep`; needs no scan |
|
|
181
|
+
|
|
182
|
+
`usages` ends with the lines `git grep` finds that the graph could not link, so
|
|
183
|
+
it never shows less than a plain search.
|
|
181
184
|
|
|
182
185
|
```
|
|
183
186
|
Shortest path (4 hops):
|
|
@@ -194,8 +197,7 @@ so it is labelled rather than presented as fact.
|
|
|
194
197
|
**A stored index can go stale, and this one is not allowed to.** Every graph
|
|
195
198
|
query hashes the working tree first and re-parses whatever changed before
|
|
196
199
|
answering, so it cannot report a line the source has already moved past. The
|
|
197
|
-
|
|
198
|
-
have been scanned, but correctness does not depend on it having run.
|
|
200
|
+
hooks refresh in the background instead, so they never wait.
|
|
199
201
|
|
|
200
202
|
Traversal is keyed on symbol id rather than name. Keying by name would merge
|
|
201
203
|
every same-named symbol into one node, and a repository with a `run` in each
|
package/docs/setup-guide.md
CHANGED
|
@@ -1,36 +1,13 @@
|
|
|
1
|
-
# Setup guide
|
|
1
|
+
# Setup guide
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
listed under 0.10.0 in the [changelog](../CHANGELOG.md).
|
|
5
|
-
|
|
6
|
-
claude-db works after one install command. This guide covers what comes after that: how to check it
|
|
7
|
-
is working, how to give it a head start, which habits and settings change the results most, and what
|
|
8
|
-
it costs. Where a recommendation rests on a measurement, the number is given. The measurements are in
|
|
9
|
-
[memory-improvements.md](https://github.com/Avijit07x/claude-db/blob/main/docs/memory-improvements.md), and how it all works is in
|
|
3
|
+
Get the best results from claude-db in five steps. For how it works inside, see
|
|
10
4
|
[how-it-works.md](./how-it-works.md).
|
|
11
5
|
|
|
12
|
-
## The short version
|
|
13
|
-
|
|
14
|
-
1. Use Node 22.16 or newer, and a git repository.
|
|
15
|
-
2. `npm install -g claude-db`
|
|
16
|
-
3. In your project: `claude-db install --project`
|
|
17
|
-
4. Keep the personal files out of git (`.mcp.json`, `CLAUDE.local.md`).
|
|
18
|
-
5. Restart Claude Code.
|
|
19
|
-
6. Check it: `claude-db status` and `claude-db doctor`.
|
|
20
|
-
7. Give it a head start: `claude-db flush`, `claude-db scan`, `claude-db seed --from-git`.
|
|
21
|
-
8. Work as usual, and look again with `claude-db status` after a day.
|
|
22
|
-
|
|
23
|
-
The rest of this guide explains each step and what to do after it.
|
|
24
|
-
|
|
25
6
|
## 1. Requirements
|
|
26
7
|
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
| A git repository | `scan` and `seed` read your project through git, and the project's folder path is what its memory is filed under |
|
|
31
|
-
| Claude Code, logged in | Two background features call Claude Haiku through your own login (see [cost and privacy](#7-cost-and-privacy)). The terminal CLI and the VS Code extension both work |
|
|
32
|
-
|
|
33
|
-
Nothing else is required. Postgres, MongoDB and the local embedding model are optional.
|
|
8
|
+
- Node 22.16 or newer (`node -v`)
|
|
9
|
+
- A git repository
|
|
10
|
+
- Claude Code, logged in
|
|
34
11
|
|
|
35
12
|
## 2. Install
|
|
36
13
|
|
|
@@ -40,309 +17,80 @@ cd your-project
|
|
|
40
17
|
claude-db install --project
|
|
41
18
|
```
|
|
42
19
|
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
### One project or the whole machine
|
|
46
|
-
|
|
47
|
-
| | `claude-db install --project` | `claude-db install` |
|
|
48
|
-
| ------------------- | ----------------------------------------- | ----------------------------------------------- |
|
|
49
|
-
| Applies to | this repository only | every project you open on this machine |
|
|
50
|
-
| Hooks go in | `.claude/settings.local.json` in the repo | `~/.claude/settings.json` |
|
|
51
|
-
| Memory instructions | `CLAUDE.local.md` in the repo | `~/.claude/CLAUDE.md` |
|
|
52
|
-
| MCP server in | `.mcp.json` in the repo | your Claude Code user config (`~/.claude.json`) |
|
|
53
|
-
| Good for | trying it, or keeping it off some repos | using it everywhere without thinking about it |
|
|
54
|
-
|
|
55
|
-
Memory itself is always one database for the whole machine (`~/.claude-memory/memory.db`), filed by
|
|
56
|
-
project. The choice above only decides where claude-db is switched on.
|
|
20
|
+
Then restart Claude Code. Hooks and the MCP server load only when Claude Code starts.
|
|
57
21
|
|
|
58
|
-
|
|
22
|
+
- Use `claude-db install` instead to switch it on for every project on this machine.
|
|
23
|
+
- Keep `.mcp.json` and `CLAUDE.local.md` out of git. They hold personal paths and rules.
|
|
59
24
|
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
| Hook | What it does |
|
|
63
|
-
| -------------------------- | ----------------------------------------------------------------------- |
|
|
64
|
-
| SessionStart | Shows what matters at the start of a chat, and starts background upkeep |
|
|
65
|
-
| UserPromptSubmit | Saves the previous turn and looks for memory that fits your new prompt |
|
|
66
|
-
| PreToolUse (every tool) | Hands Claude the memory Haiku picked, with its first tool call |
|
|
67
|
-
| PreToolUse (Bash and Grep) | Points symbol searches at the code graph instead of grep |
|
|
68
|
-
| SessionEnd | Saves the last turn and starts turning the chat into facts |
|
|
69
|
-
|
|
70
|
-
It also writes a standing instruction ("search memory before asking the user to re-explain") and three
|
|
71
|
-
skills: `/cdb-scan`, `/catchup` and `/handoff`. If you already have a skill with the same name, claude-db keeps
|
|
72
|
-
yours and says so.
|
|
73
|
-
|
|
74
|
-
### Keep personal files out of git
|
|
75
|
-
|
|
76
|
-
`.mcp.json` holds an absolute path on your machine, so committing it breaks the project for everyone
|
|
77
|
-
else. `CLAUDE.local.md` and `.claude/settings.local.json` are meant to be personal too. Make sure all
|
|
78
|
-
three are ignored:
|
|
79
|
-
|
|
80
|
-
```bash
|
|
81
|
-
printf '\n.mcp.json\nCLAUDE.local.md\n.claude/settings.local.json\n' >> .gitignore
|
|
82
|
-
```
|
|
83
|
-
|
|
84
|
-
The installer only reminds you about `.mcp.json`, and only when no `.gitignore` lists it.
|
|
85
|
-
|
|
86
|
-
### Restart Claude Code
|
|
87
|
-
|
|
88
|
-
The MCP server and the hooks are loaded when Claude Code starts. A session that was already open does
|
|
89
|
-
not have them.
|
|
90
|
-
|
|
91
|
-
## 3. Check that it works
|
|
92
|
-
|
|
93
|
-
```bash
|
|
94
|
-
claude-db status
|
|
95
|
-
```
|
|
96
|
-
|
|
97
|
-
Right after install you should see this, with your own paths:
|
|
98
|
-
|
|
99
|
-
```text
|
|
100
|
-
project : ~/shop
|
|
101
|
-
database : ~/.claude-memory/memory.db
|
|
102
|
-
hooks : this project
|
|
103
|
-
mcp : registered (~/shop/.mcp.json)
|
|
104
|
-
sessions : 0 recorded for this project
|
|
105
|
-
worked : never
|
|
106
|
-
recorded : never
|
|
107
|
-
facts : 0 for this project, 0 about you
|
|
108
|
-
waiting : 0 chat(s) not yet turned into facts
|
|
109
|
-
pick : on (haiku), 0 of 150 picks used today
|
|
110
|
-
```
|
|
111
|
-
|
|
112
|
-
"Nothing recorded yet" is normal here. Memory is written as you work, only for turns that changed
|
|
113
|
-
something, so a chat of questions leaves nothing behind. After your first real session, `sessions`
|
|
114
|
-
and `recorded` fill in.
|
|
25
|
+
## 3. Check it works
|
|
115
26
|
|
|
116
27
|
```bash
|
|
117
28
|
claude-db doctor
|
|
29
|
+
claude-db status
|
|
118
30
|
```
|
|
119
31
|
|
|
120
|
-
`doctor`
|
|
121
|
-
|
|
122
|
-
test memory, searches for it, reads it back and deletes it, and tells you which step failed if any.
|
|
32
|
+
`doctor` should end with `wiring : ok`. After your first real session, `status` shows what was
|
|
33
|
+
recorded. Nothing is saved for a chat that only asked questions, and that is normal.
|
|
123
34
|
|
|
124
35
|
## 4. Give it a head start
|
|
125
36
|
|
|
126
|
-
A fresh install has nothing to recall.
|
|
127
|
-
|
|
128
|
-
| Step | Command | What it does | Cost |
|
|
129
|
-
| ------------------------------------ | --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ |
|
|
130
|
-
| Load your past chats | `claude-db flush` | Reads the chats Claude Code already saved for this project and turns them into memory. Claude Code keeps chat files for about 30 days, so do this early | none |
|
|
131
|
-
| Map the code | `claude-db scan` | Stores every symbol and how they connect. About a second on a mid-size repo. After the first scan it refreshes itself at each session start | none |
|
|
132
|
-
| Read the git history | `claude-db seed --from-git` | Turns your commit history into memory so search has something to match | none |
|
|
133
|
-
| Or do the mapping from inside Claude | `/cdb-scan` | A skill that builds the graph, then writes five notes about your stack, layout, conventions, workflows and architecture | a normal chat turn |
|
|
134
|
-
| Ask where you stopped | `/catchup` | Prints done, open and next from the last chat, the recorded to-dos, the last handoff and git. Writes nothing. The raw facts are also in `claude-db catchup` | a normal chat turn |
|
|
135
|
-
| Hand work to the next chat | `/handoff` | Writes a short note (done, open, next), saves it as the project's one current handoff and prints it. The next chat sees it at the start for 14 days | a normal chat turn |
|
|
136
|
-
| State your standing rules | `claude-db remember "always use pnpm in this repo"` | Stored as a rule for this project and recalled when relevant | none |
|
|
37
|
+
A fresh install has nothing to recall. Run these once:
|
|
137
38
|
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
39
|
+
| Command | What you get |
|
|
40
|
+
| --------------------------- | ---------------------------------------------------------------- |
|
|
41
|
+
| `claude-db flush` | Your past chats for this project, loaded into memory |
|
|
42
|
+
| `claude-db scan` | A map of your code, so Claude can find symbols and their callers |
|
|
43
|
+
| `claude-db seed --from-git` | Your commit history, loaded into memory |
|
|
143
44
|
|
|
144
|
-
|
|
45
|
+
Old chats are also turned into short facts in the background, newest first, within a daily limit.
|
|
145
46
|
|
|
146
|
-
|
|
147
|
-
[memory-improvements.md](https://github.com/Avijit07x/claude-db/blob/main/docs/memory-improvements.md).
|
|
47
|
+
## 5. Work in ways that help
|
|
148
48
|
|
|
149
|
-
- **Be specific.**
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
- **
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
useful. A turn in which Claude uses no tools never shows a pick.
|
|
156
|
-
- **Say why.** "We chose a websocket because polling hammered the API" becomes a decision with its
|
|
157
|
-
reason. "That approach failed because..." becomes a dead end. These are what a later chat needs.
|
|
158
|
-
- **State a rule once, plainly.** Tell Claude to remember it, or run `claude-db remember`.
|
|
159
|
-
- **Commit finished work.** Work that changed files stays listed as "Not committed" in `status` and at
|
|
160
|
-
the start of a chat until those files are committed.
|
|
161
|
-
- **Wrap anything private in `<private>...</private>`.** It is removed before the turn is saved.
|
|
162
|
-
- **Use `/compact` freely.** When a chat is compacted, its own decisions and open work are put back.
|
|
163
|
-
- **Keep `CLAUDE.md` for a stable overview of the project.** claude-db stores what happened, which is
|
|
164
|
-
a different job.
|
|
165
|
-
- **Look at what it holds.** `claude-db search <words>`, `claude-db stats`, and `claude-db view` for a
|
|
166
|
-
page in the browser.
|
|
49
|
+
- **Be specific.** "Make the order feed reconnect with backoff" finds memory. "ok" and "continue" do not.
|
|
50
|
+
- **Say why.** "We chose a websocket because polling hammered the API" is kept as a decision with its reason.
|
|
51
|
+
- **State a rule once.** Tell Claude to remember it, or run `claude-db remember "always use pnpm"`.
|
|
52
|
+
- **Commit finished work.** Uncommitted work stays listed as open.
|
|
53
|
+
- **Wrap private text in `<private>...</private>`.** It is removed before saving.
|
|
54
|
+
- **Use `/catchup` when you return and `/handoff` when you stop.**
|
|
167
55
|
|
|
168
|
-
##
|
|
56
|
+
## Cost and privacy
|
|
169
57
|
|
|
170
|
-
|
|
171
|
-
It is created the first time a command changes a setting, such as `claude-db pick off`,
|
|
172
|
-
`claude-db distill off` or `claude-db use`. Edit it by hand for the rest, and list only the keys you
|
|
173
|
-
want to change.
|
|
58
|
+
Two small background features call Claude Haiku through your own login:
|
|
174
59
|
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
| `pick.enabled` | `true` | Let Haiku pick the memory shown with a prompt | you want no Claude usage for this (`claude-db pick off`) |
|
|
178
|
-
| `pick.dailyLimit` | `150` | Most picks a day. After that, only strong word matches are shown | you work a lot in one day |
|
|
179
|
-
| `pick.model` | `haiku` | `haiku`, `sonnet` or `opus` | almost never; Haiku was the one measured |
|
|
180
|
-
| `distill.enabled` | `true` | Turn finished chats into facts | you want no Claude usage for this (`claude-db distill off`) |
|
|
181
|
-
| `distill.dailyLimit` | `30` | Most fact-making calls a day | you have many old chats to catch up on |
|
|
182
|
-
| `distill.backfillDays` | `90` | How far back older chats are turned into facts | you want a shorter or longer reach |
|
|
183
|
-
| `inject.perPrompt` | `true` | Show related memory with prompts at all | you want memory only at the start of a chat |
|
|
184
|
-
| `inject.minOverlap` | `2` | Meaningful words a memory must share with the prompt | almost never; 2 was the best floor measured |
|
|
185
|
-
| `inject.promptResults` | `2` | Most memories shown with one prompt | you want more or fewer lines |
|
|
186
|
-
| `project.remote` | `origin` | The git remote that names a project | your main remote is not `origin` (a fork's `upstream`) |
|
|
187
|
-
| `updates` | `notify` | `notify`, `auto` or `off` | you want updates installed for you, or never checked |
|
|
188
|
-
| `embeddings.provider` | `auto` | `auto`, `local`, `builtin` or `none` | you install the optional embedding model, or want none |
|
|
60
|
+
- Picking the best memory for a prompt (up to 150 a day).
|
|
61
|
+
- Turning finished chats into facts (up to 30 a day).
|
|
189
62
|
|
|
190
|
-
|
|
63
|
+
Turn either off with `claude-db pick off` and `claude-db distill off`. Memory is still recorded and
|
|
64
|
+
searched without them, but fewer prompts get relevant memory. Secrets such as API keys and `.env`
|
|
65
|
+
files are never stored or sent.
|
|
191
66
|
|
|
192
|
-
|
|
67
|
+
## Teams and several machines
|
|
193
68
|
|
|
194
|
-
|
|
195
|
-
|
|
196
|
-
```json
|
|
197
|
-
{
|
|
198
|
-
"pick": { "enabled": false },
|
|
199
|
-
"distill": { "enabled": false }
|
|
200
|
-
}
|
|
201
|
-
```
|
|
202
|
-
|
|
203
|
-
The cost is quality. Without Haiku, a prompt only gets memory when the closest one shares four
|
|
204
|
-
meaningful words with it. In testing that showed memory on about 12% of prompts, and it was useful
|
|
205
|
-
43% of the time, against about 6 to 7 in 10 with Haiku. No new facts are made, so the start of a
|
|
206
|
-
chat shows the facts it already has, or recent session summaries if there are none.
|
|
207
|
-
|
|
208
|
-
**Heavy use.** Raise the limits if you hit them. `claude-db pick` and `claude-db distill` show how
|
|
209
|
-
much of today's limit is used:
|
|
210
|
-
|
|
211
|
-
```json
|
|
212
|
-
{
|
|
213
|
-
"pick": { "dailyLimit": 400 },
|
|
214
|
-
"distill": { "dailyLimit": 60 }
|
|
215
|
-
}
|
|
216
|
-
```
|
|
217
|
-
|
|
218
|
-
### Better embeddings are optional
|
|
219
|
-
|
|
220
|
-
The built-in embedder works without installing anything. For semantic matching in `search`:
|
|
221
|
-
|
|
222
|
-
```bash
|
|
223
|
-
npm install -g @xenova/transformers
|
|
224
|
-
claude-db reembed
|
|
225
|
-
```
|
|
226
|
-
|
|
227
|
-
This is a large download (about 200 MB of libraries plus a model). It is not needed for picking, and
|
|
228
|
-
its effect on the memory shown with prompts was not measured.
|
|
229
|
-
|
|
230
|
-
## 7. Cost and privacy
|
|
231
|
-
|
|
232
|
-
Nothing leaves your machine except the things below, and each can be turned off.
|
|
233
|
-
|
|
234
|
-
| What | When | What is sent | Cost | Limit | Turn it off |
|
|
235
|
-
| ------------- | ---------------------------- | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | ---------- | ----------------------- |
|
|
236
|
-
| Picking | A prompt has related memory | Your prompt, the end of Claude's previous reply, and up to ten memory excerpts of 600 characters, all redacted | About 3,000 input and 100 output Haiku tokens per pick | 150 a day | `claude-db pick off` |
|
|
237
|
-
| Facts | After a chat ends | The chat's saved, redacted text, in pieces of about 40,000 characters | One Haiku call per piece | 30 a day | `claude-db distill off` |
|
|
238
|
-
| Update check | Once a day | A request to the npm registry | none | once a day | `"updates": "off"` |
|
|
239
|
-
| Your database | Only if you set a remote one | Your memory | depends on the host | none | `claude-db use <path>` |
|
|
240
|
-
|
|
241
|
-
Both Haiku features go through your own Claude Code login, so they count against your plan like any
|
|
242
|
-
other use. Haiku is the lightest model, and a pick is small next to an ordinary chat turn. A failed
|
|
243
|
-
call pauses that feature for an hour, then six hours, then a day if calls keep failing, while recording
|
|
244
|
-
carries on. `claude-db status` shows the reason.
|
|
245
|
-
|
|
246
|
-
What is never stored: `.env` files, anything under `secrets/`, `node_modules` and `.git/`. Text in
|
|
247
|
-
`<private>...</private>` is stripped. API keys, tokens, private keys, connection-string passwords and
|
|
248
|
-
`NAME=value` secrets are redacted before anything is saved or sent. `claude-db redact` re-applies the
|
|
249
|
-
current rules to memory saved earlier; it also runs once on its own after an update.
|
|
250
|
-
|
|
251
|
-
One limit to know about: a secret you paste into a chat also stays in Claude Code's own chat file,
|
|
252
|
-
which claude-db does not edit. If you paste a real secret, rotate it.
|
|
253
|
-
|
|
254
|
-
## 8. Teams and several machines
|
|
255
|
-
|
|
256
|
-
SQLite is the default and needs no setup. To share memory, point claude-db at a database everyone can
|
|
257
|
-
reach:
|
|
69
|
+
By default memory is one SQLite file on your machine. To share it, point everyone at one database:
|
|
258
70
|
|
|
259
71
|
```bash
|
|
260
72
|
npm install -g pg
|
|
261
73
|
claude-db use "postgres://user:pass@host:5432/memory"
|
|
262
74
|
```
|
|
263
75
|
|
|
264
|
-
|
|
265
|
-
|
|
266
|
-
address, and warns if the database already holds tables that are not claude-db's. Give it a database
|
|
267
|
-
of its own.
|
|
268
|
-
|
|
269
|
-
- **Projects are matched by git remote.** A repository with an `origin` remote is one project wherever it
|
|
270
|
-
is cloned, so `github.com/acme/shop` on your laptop and on your Mac share memory. `ssh` and `https`
|
|
271
|
-
addresses of the same repository match, and any token in the address is never stored. A folder with no
|
|
272
|
-
remote is matched by its path, as before. A fork has its own remote, so it is its own project. Set
|
|
273
|
-
`project.remote` to use a remote other than `origin`. Memory saved before this, under a folder path, is
|
|
274
|
-
still found and is not moved. `claude-db merge <old-path> --yes` still works for a folder with no remote.
|
|
275
|
-
- **Personal rules stay personal.** A rule about how you like to work is filed under your git email,
|
|
276
|
-
so it follows you into every project and never reaches a teammate on a shared database. Set
|
|
277
|
-
`git config user.email` so it is filed under the right name. Everything else belongs to the
|
|
278
|
-
project and is shared.
|
|
279
|
-
- **Two databases, one memory.** `claude-db sync <url>` merges two databases in both directions, so a
|
|
280
|
-
laptop and a desktop can each work offline and reconcile later. `claude-db export` and
|
|
281
|
-
`claude-db import` do the same with a file.
|
|
282
|
-
- **Use a restricted account.** Connection strings are redacted whenever claude-db prints them, but
|
|
283
|
-
the account should only be able to reach its own database.
|
|
284
|
-
|
|
285
|
-
## 9. Keep it healthy
|
|
76
|
+
For MongoDB, install `mongodb` and use a `mongodb+srv://` address. Clones of one repository share
|
|
77
|
+
memory by git remote, so every machine must run 0.11.0 or newer.
|
|
286
78
|
|
|
287
|
-
|
|
288
|
-
| ------------------------- | ---------------------------------- | --------------------------------------------------------------------- |
|
|
289
|
-
| Now and then | `claude-db status` | Wired up, last recorded, open work, how many picks used today |
|
|
290
|
-
| Now and then | `claude-db stats` | What memory is made of, by kind and by area |
|
|
291
|
-
| After a big refactor | `claude-db scan` | Refreshes the code graph (it also refreshes at each session start) |
|
|
292
|
-
| When memory is stale | `claude-db prune --older-than 180` | A dry run that counts what would go; add `--yes` to delete |
|
|
293
|
-
| When something is wrong | `claude-db forget <id>` | Deletes a memory that turned out to be wrong, so it stops coming back |
|
|
294
|
-
| After moving a repository | `claude-db merge <old-path> --yes` | Brings memory filed under the old path across |
|
|
295
|
-
|
|
296
|
-
`claude-db uninstall --project` removes the hooks, the MCP entry and the instructions, and leaves your
|
|
297
|
-
memory untouched. Only `forget`, `prune` and `reset` delete memory, and the last two do nothing without
|
|
298
|
-
`--yes`.
|
|
299
|
-
|
|
300
|
-
## 10. Upgrading
|
|
79
|
+
## Upgrading
|
|
301
80
|
|
|
302
81
|
```bash
|
|
303
82
|
npm install -g claude-db
|
|
304
83
|
```
|
|
305
84
|
|
|
306
|
-
|
|
307
|
-
one-time jobs may run in the background, and none of them blocks a chat:
|
|
308
|
-
|
|
309
|
-
- repairing memory that an older version saved badly (`claude-db flush --repair`),
|
|
310
|
-
- re-applying secret redaction to everything already saved (`claude-db redact`),
|
|
311
|
-
- turning older chats into facts, which carries on over the next sessions within the daily limit.
|
|
312
|
-
|
|
313
|
-
Hooks that an earlier install registered are brought up to date automatically at session start, so a
|
|
314
|
-
new hook arrives without running `install` again. The first chat after you get facts says so once, and
|
|
315
|
-
how to switch that off with `claude-db distill off`.
|
|
316
|
-
|
|
317
|
-
## 11. When something is off
|
|
318
|
-
|
|
319
|
-
| What you see | Check |
|
|
320
|
-
| ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
321
|
-
| Nothing is recorded | Did you restart Claude Code after installing? Was `install` run in this repository? Did any turn change a file? Questions and read-only commands are skipped by design |
|
|
322
|
-
| Memory rarely shows up | Early on there is little to find, so run the head start steps in section 4. Prompts of one or two words, or filler, get none. Run `claude-db pick`: it says if picking is off, paused after a failed call, or past today's limit |
|
|
323
|
-
| Memory never shows in a chat of questions | Picks arrive with Claude's first tool call, so a turn with no tools never shows one |
|
|
324
|
-
| `doctor` says `registered 2x` | Run `claude-db install` again. It replaces its own entries |
|
|
325
|
-
| Install stops with a Node version message | Upgrade to Node 22.16 or newer |
|
|
326
|
-
| `reachable: no` | For Postgres or MongoDB, install the driver (`npm install -g pg` or `npm install -g mongodb`) and check `CLAUDE_DB_URL` is not set to something old |
|
|
327
|
-
| A moved repository looks empty | A repository with a remote keeps its memory. With no remote, run `claude-db merge <old-path> --yes` |
|
|
328
|
-
| Search got worse after adding the embedding model | Run `claude-db reembed` |
|
|
329
|
-
|
|
330
|
-
The [troubleshooting page](https://claude-db.vercel.app/docs/troubleshooting) covers the rest.
|
|
85
|
+
Then restart Claude Code. Memory is kept.
|
|
331
86
|
|
|
332
|
-
##
|
|
87
|
+
## When something is off
|
|
333
88
|
|
|
334
|
-
|
|
335
|
-
|
|
336
|
-
|
|
337
|
-
|
|
338
|
-
|
|
339
|
-
| `~/.claude-memory/pick/` | Picks in flight and today's pick count |
|
|
340
|
-
| `~/.claude-memory/distill/` | Today's fact-making count |
|
|
341
|
-
| `~/.claude-memory/reingest/`, `redact/` | Marks that a one-time job has finished, per project or database |
|
|
342
|
-
| `.claude/settings.local.json` | The hooks, for a project install |
|
|
343
|
-
| `.mcp.json` | The MCP server, for a project install |
|
|
344
|
-
| `CLAUDE.local.md` | The standing instruction to search memory |
|
|
345
|
-
| `.claude/skills/cdb-scan/` | The `/cdb-scan` skill |
|
|
346
|
-
| `.claude/skills/catchup/`, `handoff/` | The `/catchup` and `/handoff` skills |
|
|
89
|
+
- **Nothing recorded:** restart Claude Code, and check that `install` ran in this repository.
|
|
90
|
+
- **Memory rarely shows up:** run the head start steps, and run `claude-db pick` to see if picking
|
|
91
|
+
is off or at its limit.
|
|
92
|
+
- **`doctor` shows `reachable: no`:** for Postgres or MongoDB, install the driver (`pg` or `mongodb`).
|
|
93
|
+
- **Remove it:** `claude-db uninstall --project`. Your memory is kept.
|
|
347
94
|
|
|
348
|
-
|
|
95
|
+
Commands are in the [README](../README.md) and `claude-db --help`. Every setting is listed in
|
|
96
|
+
[architecture.md](./architecture.md).
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "claude-db",
|
|
3
|
-
"version": "0.
|
|
4
|
-
"description": "
|
|
3
|
+
"version": "0.12.0",
|
|
4
|
+
"description": "Free, open-source memory for Claude Code. Remembers why decisions were made and maps your code. Your own database (SQLite, Postgres or MongoDB), no cloud, no subscription.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"type": "module",
|
|
7
7
|
"bin": {
|
|
@@ -45,24 +45,28 @@
|
|
|
45
45
|
"bench:tokens": "node scripts/bench-tokens.mjs",
|
|
46
46
|
"bench:ab": "node scripts/bench-ab.mjs",
|
|
47
47
|
"bench:inject": "node scripts/bench-inject.mjs",
|
|
48
|
+
"bench:usages": "node scripts/bench-usages.mjs",
|
|
48
49
|
"postinstall": "node -e \"const v=process.versions.node.split('.').map(Number); if(v[0]<22||(v[0]===22&&v[1]<16)){console.error('\\n claude-db needs Node >= 22.16 (its builtin SQLite has full-text search from there). You have '+process.versions.node+'.\\n');process.exit(1)}\"",
|
|
49
50
|
"prepublishOnly": "npm run build && npm test",
|
|
50
51
|
"format": "prettier --write .",
|
|
51
52
|
"format:check": "prettier --check ."
|
|
52
53
|
},
|
|
53
54
|
"dependencies": {
|
|
54
|
-
"@ast-grep/lang-go": "^0.0.6",
|
|
55
|
-
"@ast-grep/lang-python": "^0.0.6",
|
|
56
|
-
"@ast-grep/lang-ruby": "^0.0.7",
|
|
57
|
-
"@ast-grep/lang-rust": "^0.0.7",
|
|
58
55
|
"@ast-grep/napi": "^0.45.0",
|
|
59
56
|
"@modelcontextprotocol/sdk": "^1.30.0",
|
|
60
57
|
"graphology": "^0.26.0",
|
|
61
58
|
"graphology-shortest-path": "^2.1.0",
|
|
59
|
+
"oxc-resolver": "^11.24.2",
|
|
62
60
|
"zod": "^4.4.3"
|
|
63
61
|
},
|
|
64
62
|
"devDependencies": {
|
|
65
63
|
"@arethetypeswrong/cli": "^0.18.5",
|
|
64
|
+
"@ast-grep/lang-go": "^0.0.6",
|
|
65
|
+
"@ast-grep/lang-java": "^0.0.7",
|
|
66
|
+
"@ast-grep/lang-kotlin": "0.0.7",
|
|
67
|
+
"@ast-grep/lang-python": "^0.0.6",
|
|
68
|
+
"@ast-grep/lang-ruby": "^0.0.7",
|
|
69
|
+
"@ast-grep/lang-rust": "^0.0.7",
|
|
66
70
|
"@eslint/js": "^10.0.1",
|
|
67
71
|
"@types/node": "^22.20.1",
|
|
68
72
|
"c8": "^12.0.0",
|
|
@@ -124,5 +128,12 @@
|
|
|
124
128
|
"author": "Avijit Dey",
|
|
125
129
|
"publishConfig": {
|
|
126
130
|
"access": "public"
|
|
131
|
+
},
|
|
132
|
+
"optionalDependencies": {
|
|
133
|
+
"claude-db-grammars-linux-x64": "0.12.0",
|
|
134
|
+
"claude-db-grammars-linux-arm64": "0.12.0",
|
|
135
|
+
"claude-db-grammars-darwin-x64": "0.12.0",
|
|
136
|
+
"claude-db-grammars-darwin-arm64": "0.12.0",
|
|
137
|
+
"claude-db-grammars-win32-x64": "0.12.0"
|
|
127
138
|
}
|
|
128
139
|
}
|
package/skills/catchup/SKILL.md
CHANGED
|
@@ -18,6 +18,8 @@ with nothing in it is left out.
|
|
|
18
18
|
- `Last chat` is the newest recorded chat, with a few lines of the work done in it.
|
|
19
19
|
- `Still to do` are to-dos found in earlier chats.
|
|
20
20
|
- `Not committed yet` is recorded work that no commit has covered.
|
|
21
|
+
- `Decisions and dead ends` are what was chosen or ruled out, with the reason.
|
|
22
|
+
- `Branch` says which branch you are on and how many files are uncommitted.
|
|
21
23
|
- `Git status` and `Recent commits` are the live state of the repository.
|
|
22
24
|
|
|
23
25
|
If the output is `Nothing recorded for this project yet.`, say exactly that and stop.
|