@knowledgine/cli 0.5.0 → 0.6.1

package/dist/templates/skills/knowledgine-suggest/references.js

@@ -1,121 +0,0 @@
-export const REFERENCES = {
-    "context-patterns.md": `# Context Patterns
-
-How to extract effective context signals from your current work to generate meaningful
-knowledge suggestions.
-
----
-
-## Context Signal Types
-
-### 1. File Path Context
-
-The file path is often the most precise context signal. It encodes module, feature area,
-and component type simultaneously.
-
-**How to use**:
-- Pass the file path to \`find_related(filePath: "<path>")\` directly
-- Extract path segments for search queries
-
-**Examples**:
-| File Path | Extracted Query |
-|-----------|-----------------|
-| \`src/commands/setup.ts\` | \`"setup command configuration"\` |
-| \`packages/core/src/config/config-loader.ts\` | \`"config loader configuration"\` |
-| \`packages/ingest/src/plugins/github.ts\` | \`"github ingest plugin"\` |
-
-### 2. Task Description Context
-
-Transform the task description into a knowledge query by extracting nouns and
-technical terms.
-
-**Pattern**:
-\`\`\`
-Task: "Add support for TOML config files in the setup command"
-Query: "TOML configuration setup"
-Query: "config file format"
-\`\`\`
-
-**Pattern**:
-\`\`\`
-Task: "Fix the entity extraction pipeline to handle empty documents"
-Query: "entity extraction empty document"
-Query: "edge case null handling entity"
-\`\`\`
-
-### 3. Error Message Context
-
-When starting work to fix a specific error, use the error as the primary signal.
-
-**Pattern**:
-\`\`\`
-Error: "SQLITE_ERROR: table entities has no column 'confidence'"
-Query keyword: "SQLITE_ERROR entities column"
-Query keyword: "migration entities table"
-\`\`\`
-
-### 4. Feature Area Context
-
-When working on a broad feature, search for the feature domain.
-
-**Examples**:
-| Feature Area | Context Query |
-|-------------|---------------|
-| Authentication | \`"authentication session token"\` |
-| Search | \`"search_knowledge FTS5 semantic"\` |
-| Ingest pipeline | \`"ingest plugin markdown"\` |
-| MCP server | \`"MCP server start file watcher"\` |
-
----
-
-## Multi-Signal Queries
-
-Combine 2–3 signals for more targeted results:
-
-\`\`\`
-// File + task
-query: "config-loader TOML parsing"
-
-// Component + problem type
-query: "KnowledgeRepository null safety"
-
-// Technology + pattern
-query: "sqlite migration schema change"
-\`\`\`
-
----
-
-## Using find_related for Graph Traversal
-
-After finding an initial relevant note, use \`find_related\` to discover connected notes:
-
-\`\`\`
-// Found note ID "abc123" about config loading
-find_related(noteId: "abc123", limit: 10, maxHops: 2)
-
-// Or search by the current file path directly
-find_related(filePath: "packages/core/src/config/config-loader.ts", limit: 10)
-\`\`\`
-
-**maxHops guidance**:
-| maxHops | Effect |
-|---------|--------|
-| 1 | Direct references only — fast, focused |
-| 2 | One degree of separation — good default |
-| 3 | Broader graph — use for open-ended exploration |
-
----
-
-## Suggest vs Recall Decision Guide
-
-| Situation | Use |
-|-----------|-----|
-| You have a specific error message | knowledgine-recall |
-| You know exactly what to search for | knowledgine-recall |
-| You are starting work, unsure what is relevant | knowledgine-suggest |
-| You want to discover what you don't know | knowledgine-suggest |
-| You have a file path but no specific query | knowledgine-suggest |
-| You want both targeted + exploratory | suggest first, then recall |
-`,
-};
-//# sourceMappingURL=references.js.map

package/dist/templates/skills/knowledgine-suggest/references.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"references.js","sourceRoot":"","sources":["../../../../src/templates/skills/knowledgine-suggest/references.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,UAAU,GAA2B;IAChD,qBAAqB,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqHxB;CACA,CAAC"}

package/dist/templates/skills/knowledgine-suggest/skill-md.d.ts

@@ -1,2 +0,0 @@
-export declare const SKILL_MD = "---\nname: knowledgine-suggest\ndescription: >\n  Get contextual knowledge suggestions based on the current work context \u2014 the file\n  being edited, the task being performed, or the error being investigated. Invoke at\n  the start of a work session, when opening a new file, or when beginning a feature.\n  Surfaces relevant past knowledge proactively without requiring a specific query.\n---\n# knowledgine-suggest\n\n## Purpose\n\nSurface relevant knowledge from the knowledge base based on contextual signals extracted\nfrom the current work, rather than a specific search query. Suggest combines search and\ngraph traversal to bring forward knowledge you might not know to search for.\n\n## When to Use\n\n- **Starting a session** \u2014 Get context about the area you will work in\n- **Opening a new file** \u2014 Discover past knowledge about that component\n- **Beginning a feature** \u2014 Find related patterns and past decisions\n- **Before making changes** \u2014 Check for warnings or prior art on the topic\n- **Exploring an unfamiliar module** \u2014 Find related entities and notes\n\n## When NOT to Use\n\n- When you already have a specific query in mind (use knowledgine-recall instead)\n- When working on trivial mechanical tasks with no design ambiguity\n- After already calling suggest for the same file in the same session\n\n## How to Get Suggestions (MCP Tools)\n\n### Step 1: Search by context\n\n```\nsearch_knowledge(\n  query: string,   // Derived from file path, task description, or component name\n  mode: \"hybrid\",  // Hybrid gives best results for context-based queries\n  limit: 10\n)\n```\n\n### Step 2: Find related notes (if you have a note ID or file path)\n\n```\nfind_related(\n  noteId?: string,    // ID of a relevant note found in step 1\n  filePath?: string,  // Current file path being worked on\n  limit?: number,     // Max results (default 10)\n  maxHops?: number    // Graph traversal depth (default 2)\n)\n```\n\n## How to Get Suggestions (CLI Alternative)\n\n```bash\nknowledgine suggest \"<context description>\"\nknowledgine suggest --file src/commands/setup.ts\n```\n\n## Extracting Context\n\nThe quality of suggestions depends on the context you provide. Extract signals from:\n\n| Signal | Example |\n|--------|---------|\n| Current file path | `src/commands/setup.ts` |\n| Component or class name | `SetupCommand`, `KnowledgeRepository` |\n| Task description | `\"add TOML config support to setup command\"` |\n| Feature area | `\"MCP configuration\", \"entity extraction\"` |\n| Error message | `\"TypeError: Cannot set properties of undefined\"` |\n\n## Step-by-Step Instructions\n\n1. **Extract context signals** from the current task (see context-patterns.md)\n2. **Build a query** \u2014 Combine the most specific signals into a search query\n3. **Call search_knowledge** with mode: \"hybrid\" and the derived query\n4. **Review results** \u2014 Read the top 3\u20135 most relevant notes\n5. **Traverse related notes** \u2014 Call find_related with a relevant noteId or the current filePath\n6. **Summarize findings** \u2014 Note any relevant warnings, patterns, or decisions found\n7. **Proceed informed** \u2014 Use the discovered context to guide your implementation\n\n## Best Practices\n\n- Run suggest once at session start for the primary area of work\n- Combine with knowledgine-recall for targeted queries as specific issues arise\n- Prioritize notes tagged with `bug-fix` or `troubleshooting` \u2014 they contain warnings\n- Notes tagged `design-decision` are especially valuable before making changes\n\n## Reference Files\n\n- See `context-patterns.md` for how to extract effective context from your current work\n";
-//# sourceMappingURL=skill-md.d.ts.map

package/dist/templates/skills/knowledgine-suggest/skill-md.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"skill-md.d.ts","sourceRoot":"","sources":["../../../../src/templates/skills/knowledgine-suggest/skill-md.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,QAAQ,onHA4FpB,CAAC"}

package/dist/templates/skills/knowledgine-suggest/skill-md.js

@@ -1,94 +0,0 @@
-export const SKILL_MD = `---
-name: knowledgine-suggest
-description: >
-  Get contextual knowledge suggestions based on the current work context — the file
-  being edited, the task being performed, or the error being investigated. Invoke at
-  the start of a work session, when opening a new file, or when beginning a feature.
-  Surfaces relevant past knowledge proactively without requiring a specific query.
----
-# knowledgine-suggest
-
-## Purpose
-
-Surface relevant knowledge from the knowledge base based on contextual signals extracted
-from the current work, rather than a specific search query. Suggest combines search and
-graph traversal to bring forward knowledge you might not know to search for.
-
-## When to Use
-
-- **Starting a session** — Get context about the area you will work in
-- **Opening a new file** — Discover past knowledge about that component
-- **Beginning a feature** — Find related patterns and past decisions
-- **Before making changes** — Check for warnings or prior art on the topic
-- **Exploring an unfamiliar module** — Find related entities and notes
-
-## When NOT to Use
-
-- When you already have a specific query in mind (use knowledgine-recall instead)
-- When working on trivial mechanical tasks with no design ambiguity
-- After already calling suggest for the same file in the same session
-
-## How to Get Suggestions (MCP Tools)
-
-### Step 1: Search by context
-
-\`\`\`
-search_knowledge(
-  query: string,   // Derived from file path, task description, or component name
-  mode: "hybrid",  // Hybrid gives best results for context-based queries
-  limit: 10
-)
-\`\`\`
-
-### Step 2: Find related notes (if you have a note ID or file path)
-
-\`\`\`
-find_related(
-  noteId?: string,    // ID of a relevant note found in step 1
-  filePath?: string,  // Current file path being worked on
-  limit?: number,     // Max results (default 10)
-  maxHops?: number    // Graph traversal depth (default 2)
-)
-\`\`\`
-
-## How to Get Suggestions (CLI Alternative)
-
-\`\`\`bash
-knowledgine suggest "<context description>"
-knowledgine suggest --file src/commands/setup.ts
-\`\`\`
-
-## Extracting Context
-
-The quality of suggestions depends on the context you provide. Extract signals from:
-
-| Signal | Example |
-|--------|---------|
-| Current file path | \`src/commands/setup.ts\` |
-| Component or class name | \`SetupCommand\`, \`KnowledgeRepository\` |
-| Task description | \`"add TOML config support to setup command"\` |
-| Feature area | \`"MCP configuration", "entity extraction"\` |
-| Error message | \`"TypeError: Cannot set properties of undefined"\` |
-
-## Step-by-Step Instructions
-
-1. **Extract context signals** from the current task (see context-patterns.md)
-2. **Build a query** — Combine the most specific signals into a search query
-3. **Call search_knowledge** with mode: "hybrid" and the derived query
-4. **Review results** — Read the top 3–5 most relevant notes
-5. **Traverse related notes** — Call find_related with a relevant noteId or the current filePath
-6. **Summarize findings** — Note any relevant warnings, patterns, or decisions found
-7. **Proceed informed** — Use the discovered context to guide your implementation
-
-## Best Practices
-
-- Run suggest once at session start for the primary area of work
-- Combine with knowledgine-recall for targeted queries as specific issues arise
-- Prioritize notes tagged with \`bug-fix\` or \`troubleshooting\` — they contain warnings
-- Notes tagged \`design-decision\` are especially valuable before making changes
-
-## Reference Files
-
-- See \`context-patterns.md\` for how to extract effective context from your current work
-`;
-//# sourceMappingURL=skill-md.js.map