@kentwynn/kgraph 0.1.16 → 0.1.17
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
|
@@ -257,6 +257,16 @@ npm run kgraph -- "auth token refresh"
|
|
|
257
257
|
npm run kgraph -- doctor
|
|
258
258
|
```
|
|
259
259
|
|
|
260
|
+
Test the built package as a global local install:
|
|
261
|
+
|
|
262
|
+
```bash
|
|
263
|
+
npm run build
|
|
264
|
+
npm install -g .
|
|
265
|
+
kgraph --version
|
|
266
|
+
kgraph doctor
|
|
267
|
+
kgraph "auth token refresh"
|
|
268
|
+
```
|
|
269
|
+
|
|
260
270
|
Package checks:
|
|
261
271
|
|
|
262
272
|
```bash
|
|
@@ -4,7 +4,7 @@ export const claudeCodeAdapter = {
|
|
|
4
4
|
targetPath: 'CLAUDE.md',
|
|
5
5
|
instructions: `## KGraph Workflow
|
|
6
6
|
|
|
7
|
-
Before exploring the repository, run \`kgraph
|
|
7
|
+
Before exploring the repository, run \`kgraph "<topic>"\` to refresh repo intelligence and load focused context. Use /kgraph for the full automated workflow. Run \`kgraph doctor\` when setup or generated maps look wrong. Run \`kgraph scan\`, \`kgraph update\`, and \`kgraph context\` manually only when you need one specific step.
|
|
8
8
|
`,
|
|
9
9
|
commandFiles: [
|
|
10
10
|
{
|
|
@@ -12,12 +12,13 @@ Before exploring the repository, run \`kgraph context "<topic>"\` to load existi
|
|
|
12
12
|
content: `Use KGraph persistent repo intelligence for the current request.
|
|
13
13
|
|
|
14
14
|
1. Infer the topic from the user's request.
|
|
15
|
-
2. Run \`kgraph
|
|
15
|
+
2. Run \`kgraph "<topic>"\`. This refreshes maps, processes pending inbox notes, and returns focused context in one command.
|
|
16
16
|
3. Use the returned files, symbols, relationships, and cognition before broad exploration.
|
|
17
|
-
4.
|
|
18
|
-
5.
|
|
19
|
-
6.
|
|
20
|
-
7. Run \`kgraph
|
|
17
|
+
4. Run \`kgraph doctor\` when setup, maps, inbox processing, or integrations look wrong.
|
|
18
|
+
5. **After completing the work**, write a Markdown note to \`.kgraph/inbox/<slug>.md\` **only if** you discovered something a future session would need to re-derive — a gotcha, constraint, non-obvious decision, or bug. Skip capture for read-only reviews or sessions where nothing new was found. When you do capture, immediately run \`kgraph update\` or simply run \`kgraph\`.
|
|
19
|
+
6. If you created, moved, deleted, or renamed files or symbols during this session, run \`kgraph\` or \`kgraph scan\` and report the summary. Skip it otherwise.
|
|
20
|
+
7. Run \`kgraph visualize\` when the user wants to inspect the dependency graph — opens an interactive graph at http://localhost:4242 with PNG export.
|
|
21
|
+
8. Run \`kgraph history\` to review the timeline of past cognition sessions with git author attribution.
|
|
21
22
|
|
|
22
23
|
The inbox note must use this structure:
|
|
23
24
|
\`\`\`markdown
|
|
@@ -35,6 +36,11 @@ One or two sentences describing what was done.
|
|
|
35
36
|
## Decisions
|
|
36
37
|
Any architectural or implementation decisions made.
|
|
37
38
|
\`\`\`
|
|
39
|
+
`,
|
|
40
|
+
},
|
|
41
|
+
{
|
|
42
|
+
path: '.claude/commands/kgraph-doctor.md',
|
|
43
|
+
content: `Run \`kgraph doctor\` to check whether the workspace is initialized, maps exist, inbox notes are pending, and configured integrations point to real files. Summarize any failed checks and the next command to run.
|
|
38
44
|
`,
|
|
39
45
|
},
|
|
40
46
|
{
|
|
@@ -4,7 +4,7 @@ export const codexAdapter = {
|
|
|
4
4
|
targetPath: 'AGENTS.md',
|
|
5
5
|
instructions: `## KGraph Workflow
|
|
6
6
|
|
|
7
|
-
Before exploring the repository, run \`kgraph
|
|
7
|
+
Before exploring the repository, run \`kgraph "<topic>"\` to refresh repo intelligence and load focused context. The /kgraph skill handles the full automated workflow. Run \`kgraph doctor\` when setup or generated maps look wrong. Run \`kgraph scan\`, \`kgraph update\`, and \`kgraph context\` manually only when you need one specific step.
|
|
8
8
|
`,
|
|
9
9
|
commandFiles: [
|
|
10
10
|
{
|
|
@@ -19,12 +19,13 @@ description: Use KGraph persistent repo intelligence before broad repository exp
|
|
|
19
19
|
Workflow:
|
|
20
20
|
|
|
21
21
|
1. Infer the current topic from the user request.
|
|
22
|
-
2. Run \`kgraph
|
|
22
|
+
2. Run \`kgraph "<topic>"\` before broad repo exploration. This refreshes maps, processes pending inbox notes, and returns focused context in one command.
|
|
23
23
|
3. Use KGraph's returned files, symbols, relationships, and cognition as navigation hints.
|
|
24
|
-
4.
|
|
25
|
-
5.
|
|
26
|
-
6.
|
|
27
|
-
7. Run \`kgraph
|
|
24
|
+
4. Run \`kgraph doctor\` when setup, maps, inbox processing, or integrations look wrong.
|
|
25
|
+
5. **After completing the work**, write a Markdown note to \`.kgraph/inbox/<slug>.md\` **only if** you discovered something a future session would need to re-derive — a gotcha, constraint, non-obvious decision, or bug. Skip capture for read-only reviews or sessions where nothing new was found. When you do capture, immediately run \`kgraph update\` or simply run \`kgraph\`.
|
|
26
|
+
6. If you created, moved, deleted, or renamed files or symbols during this session, run \`kgraph\` or \`kgraph scan\`. Skip it otherwise.
|
|
27
|
+
7. Run \`kgraph visualize\` when the user wants to inspect the dependency graph — opens an interactive graph at http://localhost:4242 with PNG export.
|
|
28
|
+
8. Run \`kgraph history\` to review the timeline of past cognition sessions with git author attribution.
|
|
28
29
|
|
|
29
30
|
The inbox note must use this structure:
|
|
30
31
|
\`\`\`markdown
|
|
@@ -4,9 +4,10 @@ export const copilotAdapter = {
|
|
|
4
4
|
targetPath: '.github/copilot-instructions.md',
|
|
5
5
|
instructions: `## KGraph Workflow
|
|
6
6
|
|
|
7
|
-
1. **Before exploring the repository**, run \`kgraph
|
|
8
|
-
2.
|
|
9
|
-
3.
|
|
7
|
+
1. **Before exploring the repository**, run \`kgraph "<topic>"\` to refresh maps, process pending inbox notes, and load focused repo intelligence. Use the returned files, symbols, relationships, and cognition before any broad exploration.
|
|
8
|
+
2. Run \`kgraph doctor\` when setup, maps, inbox processing, or integrations look wrong.
|
|
9
|
+
3. **After completing work**, write a Markdown note to \`.kgraph/inbox/<slug>.md\` **only if** you discovered something a future session would need to re-derive — a gotcha, architectural constraint, non-obvious decision, or bug. For routine or read-only sessions where nothing new was found, skip capture entirely. When you do capture, immediately run \`kgraph update\` or simply run \`kgraph\`.
|
|
10
|
+
4. If you created, moved, deleted, or renamed files or symbols, run \`kgraph\` or \`kgraph scan\`.
|
|
10
11
|
|
|
11
12
|
The inbox note must use this structure:
|
|
12
13
|
\`\`\`markdown
|
|
@@ -26,6 +27,16 @@ Any architectural or implementation decisions made.
|
|
|
26
27
|
\`\`\`
|
|
27
28
|
`,
|
|
28
29
|
commandFiles: [
|
|
30
|
+
{
|
|
31
|
+
path: '.github/prompts/kgraph-doctor.prompt.md',
|
|
32
|
+
content: `---
|
|
33
|
+
description: Check KGraph workspace health and next actions
|
|
34
|
+
agent: agent
|
|
35
|
+
---
|
|
36
|
+
|
|
37
|
+
Run \`kgraph doctor\` to check whether the workspace is initialized, maps exist, inbox notes are pending, and configured integrations point to real files. Summarize any failed checks and the next command to run.
|
|
38
|
+
`,
|
|
39
|
+
},
|
|
29
40
|
{
|
|
30
41
|
path: '.github/prompts/kgraph-scan.prompt.md',
|
|
31
42
|
content: `---
|
|
@@ -9,9 +9,10 @@ alwaysApply: true
|
|
|
9
9
|
|
|
10
10
|
## KGraph Workflow
|
|
11
11
|
|
|
12
|
-
- **Before exploring the repository**, run \`kgraph
|
|
13
|
-
-
|
|
14
|
-
-
|
|
12
|
+
- **Before exploring the repository**, run \`kgraph "<topic>"\` to refresh maps, process pending inbox notes, and load focused repo intelligence. Use the returned files, symbols, relationships, and cognition before any broad exploration.
|
|
13
|
+
- Run \`kgraph doctor\` when setup, maps, inbox processing, or integrations look wrong.
|
|
14
|
+
- **After completing work**, write a Markdown note to \`.kgraph/inbox/<slug>.md\` (title, Key Files, Key Symbols, Decisions sections) **only if** you discovered something a future session would need to re-derive — a gotcha, constraint, non-obvious decision, or bug. Skip capture for read-only reviews or sessions where nothing new was found. When you do capture, immediately run \`kgraph update\` or simply run \`kgraph\`.
|
|
15
|
+
- If you created, moved, deleted, or renamed files or symbols, run \`kgraph\` or \`kgraph scan\`.
|
|
15
16
|
- Run \`kgraph visualize\` to open the interactive dependency graph at http://localhost:4242 with PNG export.
|
|
16
17
|
- Run \`kgraph history\` to review the timeline of past cognition sessions with git author attribution.
|
|
17
18
|
`,
|