@kentwynn/kgraph 0.1.6 → 0.1.7

package/README.md

@@ -84,12 +84,12 @@ kgraph context "auth token refresh" --json
 
 KGraph writes local instruction files and command/prompt packs so AI tools can use the repository knowledge layer during normal coding chats.
 
-| Integration | Always-on guidance | KGraph command assets |
-| --- | --- | --- |
-| Codex | `AGENTS.md` | `.agents/skills/kgraph/SKILL.md` |
+| Integration    | Always-on guidance                | KGraph command assets              |
+| -------------- | --------------------------------- | ---------------------------------- |
+| Codex          | `AGENTS.md`                       | `.agents/skills/kgraph/SKILL.md`   |
 | GitHub Copilot | `.github/copilot-instructions.md` | `.github/prompts/kgraph.prompt.md` |
-| Cursor | `.cursor/rules/kgraph.mdc` | Built into the KGraph Cursor rule |
-| Claude Code | `CLAUDE.md` | `.claude/commands/kgraph.md` |
+| Cursor         | `.cursor/rules/kgraph.mdc`        | Built into the KGraph Cursor rule  |
+| Claude Code    | `CLAUDE.md`                       | `.claude/commands/kgraph.md`       |
 
 Example:
 
@@ -150,7 +150,21 @@ KGraph stores project intelligence in local files inside `.kgraph/`. The MVP doe
 npm install
 npm run build
 npm test
+```
+
+Test a command without installing:
+
+```bash
 npm run kgraph -- init --integrations codex,cursor
+npm run kgraph -- context "auth token refresh"
+```
+
+Install the local build globally to test the `kgraph` binary end-to-end:
+
+```bash
+npm install -g .
+kgraph --version
+kgraph init --integrations codex,copilot
 ```
 
 ## Release

package/dist/integrations/adapters/claude-code.js

@@ -4,11 +4,7 @@ export const claudeCodeAdapter = {
     targetPath: 'CLAUDE.md',
     instructions: `## KGraph Workflow
 
-- Start repository work by checking \`kgraph context "<topic>"\` when the user asks about a domain, bug, workflow, or feature.
-- Convert stable discoveries from chat into Markdown notes under \`.kgraph/inbox/\`.
-- Run \`kgraph update\` to preserve those notes as durable cognition.
-- Run \`kgraph scan\` after structural code changes.
-- Run \`kgraph visualize\` when visualization support is available and the user wants to inspect the current knowledge map.
+Before exploring the repository, run \`kgraph context "<topic>"\` to load existing repo intelligence. Use /kgraph for the full automated workflow. Run \`kgraph scan\` and \`kgraph update\` manually when needed.
 `,
     commandFiles: [
         {
@@ -18,8 +14,8 @@ export const claudeCodeAdapter = {
 1. Infer the topic from the user's request.
 2. Run \`kgraph context "<topic>"\`.
 3. Use the returned files, symbols, relationships, and cognition before broad exploration.
-4. Save durable discoveries to \`.kgraph/inbox/\` and run \`kgraph update\` when appropriate.
-5. Run \`kgraph scan\` after structural changes and report the scan summary.
+4. Save durable discoveries to \`.kgraph/inbox/\` and immediately run \`kgraph update\`.
+5. If you created, moved, deleted, or renamed files or symbols during this session, run \`kgraph scan\` and report the summary. Skip it otherwise.
 `,
         },
         {

package/dist/integrations/adapters/codex.d.ts

@@ -1,2 +1,2 @@
-import type { IntegrationAdapter } from "../integration-registry.js";
+import type { IntegrationAdapter } from '../integration-registry.js';
 export declare const codexAdapter: IntegrationAdapter;

package/dist/integrations/adapters/codex.js

@@ -1,35 +1,33 @@
 export const codexAdapter = {
-    name: "codex",
-    label: "Codex",
-    targetPath: "AGENTS.md",
+    name: 'codex',
+    label: 'Codex',
+    targetPath: 'AGENTS.md',
     instructions: `## KGraph Workflow
 
-- Before broad repository exploration, run \`kgraph context "<topic>"\` to load current repo intelligence.
-- After useful debugging, architecture discovery, workflow learning, or implementation work, write a concise Markdown note into \`.kgraph/inbox/\`.
-- Run \`kgraph update\` after adding inbox notes so KGraph preserves durable cognition.
-- Run \`kgraph scan\` after file moves, function renames, refactors, or other structural changes.
-- When visualization support is available and the developer asks to inspect KGraph, run \`kgraph visualize\` and report the generated local artifact.
+Before exploring the repository, run \`kgraph context "<topic>"\` to load existing repo intelligence. The /kgraph skill handles the full automated workflow. Run \`kgraph scan\` and \`kgraph update\` manually when needed.
 `,
     commandFiles: [
         {
-            path: ".agents/skills/kgraph/SKILL.md",
+            path: '.agents/skills/kgraph/SKILL.md',
             content: `---
-name: "kgraph"
-description: "Use KGraph persistent repo intelligence for the current coding task."
+name: kgraph
+description: Use KGraph persistent repo intelligence before broad repository exploration. Use when asked about repo structure, debugging context, architecture decisions, or to avoid rediscovering what is already known.
 ---
 
-Use this skill when the user asks to use KGraph, requests repo context, or asks you to avoid rediscovering repository structure.
+# KGraph Skill
 
 Workflow:
 
 1. Infer the current topic from the user request.
 2. Run \`kgraph context "<topic>"\` before broad repo exploration.
-3. Use KGraph's files, symbols, relationships, and cognition as navigation hints.
-4. After durable discoveries, write a concise Markdown note to \`.kgraph/inbox/\`.
-5. Run \`kgraph update\` if you created an inbox note.
-6. Run \`kgraph scan\` after structural changes.
-`
-        }
+3. Use KGraph's returned files, symbols, relationships, and cognition as navigation hints.
+4. After durable discoveries, write a concise Markdown note to \`.kgraph/inbox/\` and immediately run \`kgraph update\`.
+5. If you created, moved, deleted, or renamed files or symbols during this session, run \`kgraph scan\`. Skip it otherwise.
+`,
+        },
+    ],
+    obsoleteCommandFiles: [
+        '.agents/skills/kgraph-update',
+        '.agents/skills/kgraph-scan',
     ],
-    obsoleteCommandFiles: [".agents/skills/kgraph-update", ".agents/skills/kgraph-scan"]
 };

package/dist/integrations/adapters/copilot.js

@@ -4,29 +4,9 @@ export const copilotAdapter = {
     targetPath: '.github/copilot-instructions.md',
     instructions: `## KGraph Workflow
 
-- Use \`kgraph context "<topic>"\` before scanning many files manually.
-- Preserve stable findings by creating Markdown notes in \`.kgraph/inbox/\`.
-- Use \`kgraph update\` to process chat summaries and debugging conclusions into durable cognition.
-- Use \`kgraph scan\` when code structure changes.
-- Use \`kgraph visualize\` when visualization support is available and the developer asks to inspect the repository knowledge map.
+Before exploring the repository, run \`kgraph context "<topic>"\` to load existing repo intelligence. Use /kgraph-scan and /kgraph-update for manual maintenance.
 `,
     commandFiles: [
-        {
-            path: '.github/prompts/kgraph.prompt.md',
-            content: `---
-mode: agent
-description: Use KGraph persistent repo intelligence for this request
----
-
-Use KGraph for the current task.
-
-1. If the user provided a topic, run \`kgraph context "<topic>"\` first. If not, infer a concise topic from the request.
-2. Use the returned files, symbols, relationships, and cognition before broad repository exploration.
-3. If you discover durable architecture, debugging, workflow, or gotcha knowledge, create a Markdown note in \`.kgraph/inbox/\`.
-4. If you add an inbox note, run \`kgraph update\`.
-5. If code structure changed, run \`kgraph scan\`.
-`,
-        },
         {
             path: '.github/prompts/kgraph-scan.prompt.md',
             content: `---
@@ -48,5 +28,5 @@ Run \`kgraph update\` to process any pending Markdown notes in \`.kgraph/inbox/\
 `,
         },
     ],
-    obsoleteCommandFiles: [],
+    obsoleteCommandFiles: ['.github/prompts/kgraph.prompt.md'],
 };

package/dist/integrations/adapters/cursor.d.ts

@@ -1,2 +1,2 @@
-import type { IntegrationAdapter } from "../integration-registry.js";
+import type { IntegrationAdapter } from '../integration-registry.js';
 export declare const cursorAdapter: IntegrationAdapter;

package/dist/integrations/adapters/cursor.js

@@ -1,7 +1,7 @@
 export const cursorAdapter = {
-    name: "cursor",
-    label: "Cursor",
-    targetPath: ".cursor/rules/kgraph.mdc",
+    name: 'cursor',
+    label: 'Cursor',
+    targetPath: '.cursor/rules/kgraph.mdc',
     instructions: `---
 description: Use KGraph persistent repo intelligence before broad repository exploration
 alwaysApply: true
@@ -9,11 +9,7 @@ alwaysApply: true
 
 ## KGraph Workflow
 
-- Query \`kgraph context "<topic>"\` before broad file searches when repo cognition may already exist.
-- Store durable chat, debugging, architecture, and workflow discoveries as Markdown notes in \`.kgraph/inbox/\`.
-- Run \`kgraph update\` after adding useful notes.
-- Run \`kgraph scan\` after refactors, moved folders, renamed functions, or other structure changes.
-- Run \`kgraph visualize\` when visualization support is available and the developer asks to inspect the KGraph map.
+Before exploring the repository, run \`kgraph context "<topic>"\` to load existing repo intelligence. Run \`kgraph scan\` and \`kgraph update\` manually when needed.
 `,
-    obsoleteCommandFiles: [".cursor/rules/kgraph-commands.mdc"]
+    obsoleteCommandFiles: ['.cursor/rules/kgraph-commands.mdc'],
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kentwynn/kgraph",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "description": "Persistent repo intelligence for AI coding assistants.",
   "type": "module",
   "bin": {
@@ -14,6 +14,7 @@
   "scripts": {
     "clean": "node scripts/clean-dist.mjs",
     "build": "npm run clean && tsc -p tsconfig.json",
+    "postbuild": "chmod +x dist/cli/index.js",
     "test": "vitest run",
     "kgraph": "tsx src/cli/index.ts",
     "check:artifacts": "node scripts/check-clean-artifacts.mjs",