@kentwynn/kgraph 0.1.17 → 0.1.18
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.
|
@@ -15,26 +15,28 @@ Before exploring the repository, run \`kgraph "<topic>"\` to refresh repo intell
|
|
|
15
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
17
|
4. Run \`kgraph doctor\` when setup, maps, inbox processing, or integrations look wrong.
|
|
18
|
-
5.
|
|
19
|
-
6. If
|
|
20
|
-
7.
|
|
21
|
-
8. Run \`kgraph
|
|
18
|
+
5. At the end of any session that changed repository files, check the KGraph capture workflow before finishing.
|
|
19
|
+
6. If the file change has future value, write one concise Markdown note to \`.kgraph/inbox/<slug>.md\`; otherwise explicitly skip capture as trivial.
|
|
20
|
+
7. Skip capture only for read-only work, trivial formatting, typo-only docs, dependency-only churn, mechanical cleanup with no future value, or sessions where no repo files changed.
|
|
21
|
+
8. Do not run KGraph repeatedly. Run it once at the start with \`kgraph "<topic>"\`. If repo files changed, write any needed inbox note first, then run \`kgraph\` once at the end.
|
|
22
|
+
9. Run \`kgraph visualize\` when the user wants to inspect the dependency graph — opens an interactive graph at http://localhost:4242 with PNG export.
|
|
23
|
+
10. Run \`kgraph history\` to review the timeline of past cognition sessions with git author attribution.
|
|
22
24
|
|
|
23
25
|
The inbox note must use this structure:
|
|
24
26
|
\`\`\`markdown
|
|
25
27
|
# <Short Title>
|
|
26
28
|
|
|
27
29
|
## Summary
|
|
28
|
-
One or two sentences describing
|
|
30
|
+
One or two sentences describing the durable change or finding.
|
|
29
31
|
|
|
30
32
|
## Key Files
|
|
31
|
-
- \`path/to/file.ts\` — what it
|
|
33
|
+
- \`path/to/file.ts\` — what changed or why it matters
|
|
32
34
|
|
|
33
35
|
## Key Symbols
|
|
34
|
-
- \`FunctionName\` — what it
|
|
36
|
+
- \`FunctionName\` — what changed or why it matters
|
|
35
37
|
|
|
36
38
|
## Decisions
|
|
37
|
-
Any
|
|
39
|
+
Any implementation or product decision future sessions should know.
|
|
38
40
|
\`\`\`
|
|
39
41
|
`,
|
|
40
42
|
},
|
|
@@ -22,26 +22,28 @@ Workflow:
|
|
|
22
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
24
|
4. Run \`kgraph doctor\` when setup, maps, inbox processing, or integrations look wrong.
|
|
25
|
-
5.
|
|
26
|
-
6. If
|
|
27
|
-
7.
|
|
28
|
-
8. Run \`kgraph
|
|
25
|
+
5. At the end of any session that changed repository files, check the KGraph capture workflow before finishing.
|
|
26
|
+
6. If the file change has future value, write one concise Markdown note to \`.kgraph/inbox/<slug>.md\`; otherwise explicitly skip capture as trivial.
|
|
27
|
+
7. Skip capture only for read-only work, trivial formatting, typo-only docs, dependency-only churn, mechanical cleanup with no future value, or sessions where no repo files changed.
|
|
28
|
+
8. Do not run KGraph repeatedly. Run it once at the start with \`kgraph "<topic>"\`. If repo files changed, write any needed inbox note first, then run \`kgraph\` once at the end.
|
|
29
|
+
9. Run \`kgraph visualize\` when the user wants to inspect the dependency graph — opens an interactive graph at http://localhost:4242 with PNG export.
|
|
30
|
+
10. Run \`kgraph history\` to review the timeline of past cognition sessions with git author attribution.
|
|
29
31
|
|
|
30
32
|
The inbox note must use this structure:
|
|
31
33
|
\`\`\`markdown
|
|
32
34
|
# <Short Title>
|
|
33
35
|
|
|
34
36
|
## Summary
|
|
35
|
-
One or two sentences describing
|
|
37
|
+
One or two sentences describing the durable change or finding.
|
|
36
38
|
|
|
37
39
|
## Key Files
|
|
38
|
-
- \`path/to/file.ts\` — what it
|
|
40
|
+
- \`path/to/file.ts\` — what changed or why it matters
|
|
39
41
|
|
|
40
42
|
## Key Symbols
|
|
41
|
-
- \`FunctionName\` — what it
|
|
43
|
+
- \`FunctionName\` — what changed or why it matters
|
|
42
44
|
|
|
43
45
|
## Decisions
|
|
44
|
-
Any
|
|
46
|
+
Any implementation or product decision future sessions should know.
|
|
45
47
|
\`\`\`
|
|
46
48
|
`,
|
|
47
49
|
},
|
|
@@ -6,8 +6,10 @@ export const copilotAdapter = {
|
|
|
6
6
|
|
|
7
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
8
|
2. Run \`kgraph doctor\` when setup, maps, inbox processing, or integrations look wrong.
|
|
9
|
-
3.
|
|
10
|
-
4. If
|
|
9
|
+
3. At the end of any session that changed repository files, check the KGraph capture workflow before finishing.
|
|
10
|
+
4. If the file change has future value, write one concise Markdown note to \`.kgraph/inbox/<slug>.md\`; otherwise explicitly skip capture as trivial.
|
|
11
|
+
5. Skip capture only for read-only work, trivial formatting, typo-only docs, dependency-only churn, mechanical cleanup with no future value, or sessions where no repo files changed.
|
|
12
|
+
6. Do not run KGraph repeatedly. Run it once at the start with \`kgraph "<topic>"\`. If repo files changed, write any needed inbox note first, then run \`kgraph\` once at the end.
|
|
11
13
|
|
|
12
14
|
The inbox note must use this structure:
|
|
13
15
|
\`\`\`markdown
|
|
@@ -77,9 +79,10 @@ argument-hint: "Brief description of what was done"
|
|
|
77
79
|
|
|
78
80
|
Capture this session into KGraph cognition.
|
|
79
81
|
|
|
80
|
-
1.
|
|
81
|
-
2.
|
|
82
|
-
3.
|
|
82
|
+
1. For any completed code or repo-file change, check whether it has future value before finishing.
|
|
83
|
+
2. Skip capture only for read-only work, trivial formatting, typo-only docs, dependency-only churn, mechanical cleanup with no future value, or sessions where no repo files changed.
|
|
84
|
+
3. Write one Markdown note to \`.kgraph/inbox/<slug>.md\` using the structure below. Use the user's message as context, but keep the note factual and concise.
|
|
85
|
+
4. Run \`kgraph\` once to process the note and refresh maps. Use \`kgraph update\` only when you intentionally want inbox processing without a scan.
|
|
83
86
|
|
|
84
87
|
Note structure:
|
|
85
88
|
\`\`\`markdown
|
|
@@ -11,8 +11,10 @@ alwaysApply: true
|
|
|
11
11
|
|
|
12
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
13
|
- Run \`kgraph doctor\` when setup, maps, inbox processing, or integrations look wrong.
|
|
14
|
-
-
|
|
15
|
-
- If
|
|
14
|
+
- At the end of any session that changed repository files, check the KGraph capture workflow before finishing.
|
|
15
|
+
- If the file change has future value, write one concise Markdown note to \`.kgraph/inbox/<slug>.md\`; otherwise explicitly skip capture as trivial.
|
|
16
|
+
- Skip capture only for read-only work, trivial formatting, typo-only docs, dependency-only churn, mechanical cleanup with no future value, or sessions where no repo files changed.
|
|
17
|
+
- Do not run KGraph repeatedly. Run it once at the start with \`kgraph "<topic>"\`. If repo files changed, write any needed inbox note first, then run \`kgraph\` once at the end.
|
|
16
18
|
- Run \`kgraph visualize\` to open the interactive dependency graph at http://localhost:4242 with PNG export.
|
|
17
19
|
- Run \`kgraph history\` to review the timeline of past cognition sessions with git author attribution.
|
|
18
20
|
`,
|