npm - @lore-ai/cli - Versions diffs - 0.1.6 - Mend

@lore-ai/cli 0.1.6

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.

Files changed (45) hide show

package/README.md +178 -0
package/dist/bin/lore.js +14666 -0
package/dist/bin/lore.js.map +1 -0
package/dist/ui/assets/Analytics-W2ANIC2s.js +1 -0
package/dist/ui/assets/ConversationDetail-Ct-hROwS.js +5 -0
package/dist/ui/assets/Conversations-iK7E6GEl.js +1 -0
package/dist/ui/assets/MarkdownPreview-2zDiish4.js +17 -0
package/dist/ui/assets/MarkdownPreview-ZgkIHsf0.css +1 -0
package/dist/ui/assets/Mcps-CCT1FQ4H.js +1 -0
package/dist/ui/assets/Overview-B_jOY8il.js +1 -0
package/dist/ui/assets/PhaseReview-B_DDY9YB.js +1 -0
package/dist/ui/assets/RepoScans-FxiMynYO.js +2 -0
package/dist/ui/assets/RepoSelector-DmPRS8kf.js +1 -0
package/dist/ui/assets/ResizablePanels-Bbb4S6Ss.js +1 -0
package/dist/ui/assets/Review-KjvS-DNP.js +3 -0
package/dist/ui/assets/ScanConversation-BonEB7pv.js +1 -0
package/dist/ui/assets/Scans-DXf2sNms.js +1 -0
package/dist/ui/assets/Skills-MvVWWoB2.js +1 -0
package/dist/ui/assets/ToolUsage-DA5MJNwl.js +33 -0
package/dist/ui/assets/Vetting-BRGVrtOA.js +1 -0
package/dist/ui/assets/index-CVSL0ryk.js +12 -0
package/dist/ui/assets/index-DYKYIfPr.css +1 -0
package/dist/ui/assets/markdown-CZuQZQX5.js +35 -0
package/dist/ui/index.html +15 -0
package/package.json +96 -0
package/prompts/analyze-feedback.md +67 -0
package/prompts/apply-refs-update.md +149 -0
package/prompts/apply-skill-update.md +151 -0
package/prompts/check-relevance.md +137 -0
package/prompts/classify-conversations.md +78 -0
package/prompts/cluster-repo-summaries.md +76 -0
package/prompts/detect-staleness.md +42 -0
package/prompts/distill-changes.md +62 -0
package/prompts/distill-decisions.md +48 -0
package/prompts/distill-patterns.md +39 -0
package/prompts/generate-changelog.md +42 -0
package/prompts/generate-references.md +192 -0
package/prompts/generate-repo-skill.md +387 -0
package/prompts/global-summary.md +55 -0
package/prompts/orchestrate-merge.md +70 -0
package/prompts/pr-description.md +49 -0
package/prompts/research-repo.md +121 -0
package/prompts/summarize-conversation.md +64 -0
package/prompts/test-mcp.md +62 -0
package/prompts/test-skill.md +72 -0

package/dist/ui/index.html ADDED Viewed

@@ -0,0 +1,15 @@
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <title>Lore Dashboard</title>
+    <link rel="icon" type="image/svg+xml" href="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 100'><text y='.9em' font-size='90'>📖</text></svg>" />
+    <script type="module" crossorigin src="/assets/index-CVSL0ryk.js"></script>
+    <link rel="modulepreload" crossorigin href="/assets/markdown-CZuQZQX5.js">
+    <link rel="stylesheet" crossorigin href="/assets/index-DYKYIfPr.css">
+  </head>
+  <body>
+    <div id="root"></div>
+  </body>
+</html>

package/package.json ADDED Viewed

@@ -0,0 +1,96 @@
+{
+  "name": "@lore-ai/cli",
+  "version": "0.1.6",
+  "description": "Automated project knowledge that writes itself. Scans git history and AI coding conversations to generate living documentation.",
+  "type": "module",
+  "bin": {
+    "lore": "./dist/bin/lore.js"
+  },
+  "publishConfig": {
+    "access": "public",
+    "registry": "https://registry.npmjs.org"
+  },
+  "scripts": {
+    "build": "tsup && vite build --config ui/vite.config.ts",
+    "build:cli": "tsup",
+    "build:ui": "vite build --config ui/vite.config.ts",
+    "dev": "tsup --watch",
+    "dev:ui": "vite --config ui/vite.config.ts",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "lint": "eslint src/ bin/",
+    "typecheck": "tsc --noEmit",
+    "build:ext": "cd extension && npm run build && npx @vscode/vsce package --no-dependencies && cursor --install-extension lore-cursor-extension-0.1.6.vsix --force",
+    "prepublishOnly": "npm run build",
+    "release": "bash scripts/release.sh"
+  },
+  "files": [
+    "dist",
+    "prompts",
+    "dist/ui"
+  ],
+  "keywords": [
+    "cli",
+    "documentation",
+    "ai",
+    "git",
+    "cursor",
+    "claude",
+    "knowledge-management"
+  ],
+  "license": "MIT",
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "dependencies": {
+    "@anthropic-ai/tokenizer": "^0.0.4",
+    "@clack/prompts": "^0.9.1",
+    "@hono/node-server": "^1.19.9",
+    "@tanstack/react-query": "^5.90.20",
+    "@vscode/sqlite3": "^5.1.12-vscode",
+    "better-sqlite3": "^12.6.2",
+    "c12": "^2.0.1",
+    "commander": "^13.1.0",
+    "consola": "^3.4.0",
+    "conventional-commits-parser": "^6.2.1",
+    "execa": "^9.5.2",
+    "globby": "^14.0.2",
+    "hono": "^4.11.5",
+    "js-tiktoken": "^1.0.21",
+    "listr2": "^8.2.5",
+    "lru-cache": "^11.2.5",
+    "nanospinner": "^1.2.2",
+    "node-cron": "^3.0.3",
+    "picocolors": "^1.1.1",
+    "react": "^19.2.3",
+    "react-dom": "^19.2.3",
+    "react-is": "^19.2.3",
+    "react-markdown": "^10.1.0",
+    "react-router-dom": "^7.12.0",
+    "recharts": "^3.7.0",
+    "rehype-highlight": "^7.0.2",
+    "remark-gfm": "^4.0.1",
+    "remark-parse": "^11.0.0",
+    "remark-stringify": "^11.0.0",
+    "simple-git": "^3.27.0",
+    "sql.js": "^1.11.0",
+    "unified": "^11.0.5",
+    "unist-util-visit": "^5.0.0",
+    "zod": "^3.24.1"
+  },
+  "devDependencies": {
+    "@tailwindcss/vite": "^4.1.18",
+    "@types/better-sqlite3": "^7.6.13",
+    "@types/node": "^22.12.0",
+    "@types/node-cron": "^3.0.11",
+    "@types/react": "^19.2.9",
+    "@types/react-dom": "^19.2.3",
+    "@types/react-is": "^19",
+    "@vitejs/plugin-react": "^5.1.2",
+    "tailwindcss": "^4.1.18",
+    "tsup": "^8.3.6",
+    "typescript": "^5.7.3",
+    "vite": "^7.3.1",
+    "vitest": "^3.0.4"
+  }
+}

package/prompts/analyze-feedback.md ADDED Viewed

@@ -0,0 +1,67 @@
+<role>
+You are a skill improvement analyst. You analyze usage feedback for Cursor skills and MCP servers, identify patterns, and propose specific improvements.
+</role>
+<task>
+Analyze the accumulated feedback for the given skill/MCP and produce an improvement plan with specific rewrite proposals.
+</task>
+<skill_content>
+{skill_content}
+</skill_content>
+<feedback_entries>
+{feedback_entries}
+</feedback_entries>
+<previous_scores>
+{previous_scores}
+</previous_scores>
+<instructions>
+- Group feedback by category and identify recurring patterns
+- Determine which rubric dimensions are weakest
+- For each weakness, propose a specific edit to the SKILL.md
+- Classify edits as minor (auto-apply) or structural (needs user approval)
+- Preserve strengths -- do not change what is working well
+- Check if feedback indicates conflicts with other skills or user rules
+- Generate unified diffs for each proposed change
+</instructions>
+<output_format>
+{
+  "overallHealth": "healthy|needs-attention|critical",
+  "strengths": ["things working well, preserve these"],
+  "weaknesses": [
+    {
+      "area": "clarity|triggerAccuracy|outputQuality|instructionCompleteness",
+      "description": "specific issue",
+      "suggestedFix": "what to change",
+      "severity": "minor|structural"
+    }
+  ],
+  "conflicts": [
+    {
+      "conflictsWith": "name",
+      "description": "...",
+      "resolution": "..."
+    }
+  ],
+  "rewrites": [
+    {
+      "reason": "why this change is needed",
+      "diff": "unified diff string",
+      "severity": "minor|structural"
+    }
+  ]
+}
+</output_format>
+<rules>
+- Respond ONLY with valid JSON matching the schema above
+- Do not wrap the response in markdown code fences
+- Be conservative: only propose changes clearly supported by feedback evidence
+- Diffs must be valid unified diff format
+- Minor changes: wording, examples, clarifications
+- Structural changes: triggers, workflows, output format, dependencies
+</rules>

package/prompts/apply-refs-update.md ADDED Viewed

@@ -0,0 +1,149 @@
+<role>
+You are a technical writer applying targeted updates to reference documentation files for an AI coding agent's skill.
+You have Read, Edit, and Bash tools to surgically update specific sections of files.
+Edit only the sections that need changes. Your stdout output is only for confirmation summaries.
+</role>
+<tools>
+You have three tools: **Read**, **Edit**, and **Bash**.
+1. **Grep first to locate relevant sections** — use Bash `grep` to find where changes are needed BEFORE reading full files:
+   ```bash
+   # Find which files and lines mention the topic from the change hints
+   grep -rn "keyword_from_change_hints" "{{SKILL_DIR}}/references/"
+   # Find heading boundaries in a specific file
+   grep -n "^## " "{{SKILL_DIR}}/references/03-topic-name.md"
+   # List reference files to see what exists
+   ls "{{SKILL_DIR}}/references/"
+   ```
+   This tells you exactly which sections to target without reading entire files into context.
+2. **Read only the targeted section** — use the Read tool with line offset/limit to read ONLY the section you need to edit, not the whole file:
+   - If grep shows the relevant section is at lines 50-80, read only that range
+   - Only read the full file if the change hints say "regenerate fully" or you need broad context
+   - Read `{{SKILL_DIR}}/SKILL.md` frontmatter (first ~10 lines) for skill scope context if needed
+3. **Edit sections surgically** using the Edit tool:
+   - Provide `old_string` (the exact existing text to replace) and `new_string` (the replacement)
+   - For reference files with sections, use headings (e.g., `## Section Name`) as edit boundaries
+   - The `old_string` MUST be unique within the file
+   - Make one Edit call per changed section
+4. **Report progress** after editing each file (best-effort, silent on failure):
+   ```bash
+   echo '{"file":"FILENAME","completed":N,"total":{{TOTAL_FILES}},"phase":"delta-refs"}' > "{{PROGRESS_FILE}}"
+   curl -s -X POST http://localhost:{{UI_PORT}}/api/events/progress \
+     -H 'Content-Type: application/json' \
+     -d '{"file":"FILENAME","completed":N,"total":{{TOTAL_FILES}},"phase":"delta-refs"}' 2>/dev/null || true
+   ```
+   The `echo` line writes a local progress file so the CLI can show progress even when the web UI is not running. Always run BOTH lines.
+5. **Fallback: full-file rewrite** — ONLY if a change hint says "regenerate fully" or changes span more than 50% of the file:
+   ```bash
+   mkdir -p "{{SKILL_DIR}}/references"
+   cat > "{{SKILL_DIR}}/FILENAME" << 'LORE_EOF'
+   (full updated content)
+   LORE_EOF
+   ```
+6. **Create new files** — when a change hint references a file that doesn't exist yet:
+   ```bash
+   mkdir -p "{{SKILL_DIR}}/references"
+   cat > "{{SKILL_DIR}}/references/NEW-FILE.md" << 'LORE_EOF'
+   (new file content)
+   LORE_EOF
+   ```
+7. **Remove stale duplicates** — after creating or updating files, check for duplicates covering the same topic:
+   ```bash
+   # List all reference files to spot duplicates
+   ls "{{SKILL_DIR}}/references/"
+   # Remove stale file if its topic is now covered by another file
+   rm -f "{{SKILL_DIR}}/references/STALE-FILE.md"
+   ```
+Do NOT read entire files when you only need to edit one section. Grep first, then read the targeted range.
+</tools>
+<installed_skills>
+The user has the following skills already installed. When updating reference docs,
+do NOT add content that duplicates what these skills already cover. Add brief
+cross-references instead ("For [topic], see the [skill-name] skill.").
+{{INSTALLED_SKILLS_DIGEST}}
+</installed_skills>
+<installed_mcps>
+The user has the following public MCP servers configured. When updating reference
+docs, if the delta introduces MCP-related patterns for public MCPs listed here,
+include them in the documentation.
+{{INSTALLED_MCPS_DIGEST}}
+</installed_mcps>
+<context>
+Repository: {{REPO_NAME}}
+Skill directory: {{SKILL_DIR}}
+<delta_analysis>
+The following analysis describes what changed in the codebase and what needs to be updated:
+{{DELTA_ANALYSIS}}
+</delta_analysis>
+<change_hints>
+Specific changes to apply per file:
+{{CHANGE_HINTS}}
+</change_hints>
+</context>
+<task>
+Apply the changes described in the delta analysis and change hints to the existing reference documentation files.
+This is a TARGETED UPDATE, not a full regeneration.
+Workflow:
+1. **Grep** to locate relevant sections — extract keywords from the change hints and grep across reference files to find which headings/sections contain the content that needs updating
+2. **Read** only the targeted section(s) — use line offset/limit based on grep results, not the full file
+3. **Edit** only the changed section(s) using the Edit tool with old_string/new_string
+4. Leave all other sections completely untouched
+5. **Report progress** after editing each file
+6. Repeat for the next file
+For each file listed in the change hints:
+- Grep to find the heading boundaries and the lines matching the change hint keywords
+- Read only the section that needs editing (use line offset/limit from grep output)
+- Use Edit to replace only that section, preserving everything else
+Do NOT read entire files when you only need to edit one section. Do NOT rewrite entire files.
+</task>
+<output_format>
+Use the Edit tool for each section that needs changes, then output a summary:
+```
+UPDATED: references/INDEX.md (1 section), references/03-skill-generation.md (2 sections)
+```
+If a change hint says "regenerate fully" for a file, or a new file needs to be created, use the Bash heredoc for that file only.
+</output_format>
+<rules>
+- **GREP FIRST**: Always grep to locate the relevant section before reading or editing. Never read an entire file when you only need one section.
+- **READ TARGETED**: Use the Read tool with line offset/limit to read only the section identified by grep. Only read a full file if the change hints say "regenerate fully."
+- **EDIT IN PLACE**: Use the Edit tool to replace only changed sections. Never rewrite an entire file unless the change hints say "regenerate fully" or changes span more than 50% of the file.
+- **SECTION BOUNDARIES**: Use headings (`## Section Name`) or distinct content blocks as natural edit boundaries. Replace the full section when its content changed.
+- **SURGICAL UPDATES**: Only modify sections relevant to the delta. Do NOT restructure or rewrite content that hasn't changed.
+- **XML STRUCTURE**: Preserve all existing XML tags. If adding new sections, wrap them in appropriate descriptive XML tags.
+- **Preserve quality**: Existing content has been vetted. Only change it when the delta analysis specifically calls for it.
+- **Cross-references**: Ensure all links between references/INDEX.md and individual reference files remain valid.
+- Use imperative form ("Use X" not "You should use X").
+- Include real code examples from the repo when documenting new patterns.
+- Concise is key — only add context the agent doesn't already know.
+- **Bash usage**: Use Bash ONLY for `grep` (search), `ls` (listing), `echo`/`curl` (progress), `mkdir -p` (directory creation), and the full-file heredoc fallback. Do NOT use Bash for reading files (use Read tool) or for small edits (use Edit tool).
+- **Heredoc delimiter**: When using the fallback, always use `LORE_EOF` (with single quotes to prevent expansion). Never use `EOF` or other common delimiters.
+- **Directory creation**: Run `mkdir -p` before writing new files to `references/` subdirectory.
+- **DEDUPLICATION**: After updates, list reference files with `ls`. If two files cover the same topic (even under different numbers/names), remove the stale one with `rm`. Maximum 8 reference files — merge related subtopics.
+- **INDEX file**: The reference folder index is `references/INDEX.md`, NOT `references/README.md`. Update INDEX.md cross-references when adding/removing files.
+</rules>

package/prompts/apply-skill-update.md ADDED Viewed

@@ -0,0 +1,151 @@
+<role>
+You are a technical writer applying targeted updates to existing AI coding skill documentation.
+You have Read, Edit, and Bash tools to surgically update specific sections of files.
+Edit only the sections that need changes. Your stdout output is only for confirmation summaries.
+Edit thoroughly — do not skip sections that the change hints indicate need updating. Verify each edit preserves surrounding context. Quality matters more than speed.
+</role>
+<tools>
+You have three tools: **Read**, **Edit**, and **Bash**.
+1. **Grep first to locate relevant sections** — use Bash `grep` to find where changes are needed BEFORE reading full files:
+   ```bash
+   # Find which files and lines mention the topic from the change hints
+   grep -n "keyword_from_change_hints" "{{SKILL_DIR}}"/*.md
+   # Find XML section boundaries in a specific file
+   grep -n "^<\|^</" "{{SKILL_DIR}}/SKILL.md"
+   # Find heading boundaries in supporting files
+   grep -n "^## " "{{SKILL_DIR}}/established-patterns.md"
+   ```
+   This tells you exactly which sections to target without reading entire files into context.
+2. **Read only the targeted section** — use the Read tool with line offset/limit to read ONLY the section you need to edit, not the whole file:
+   - If grep shows the relevant section is at lines 50-80, read only that range
+   - Only read the full file if the change hints say "regenerate fully" or you need broad context
+3. **Edit sections surgically** using the Edit tool:
+   - Provide `old_string` (the exact existing text to replace) and `new_string` (the replacement)
+   - Use XML section tags as natural edit boundaries (e.g., the full `<architecture>...</architecture>` block)
+   - The `old_string` MUST be unique within the file — XML section tags guarantee this
+   - Make one Edit call per changed section
+4. **Report progress** after editing each file (best-effort, silent on failure):
+   ```bash
+   echo '{"file":"FILENAME","completed":N,"total":{{TOTAL_FILES}},"phase":"delta-core"}' > "{{PROGRESS_FILE}}"
+   curl -s -X POST http://localhost:{{UI_PORT}}/api/events/progress \
+     -H 'Content-Type: application/json' \
+     -d '{"file":"FILENAME","completed":N,"total":{{TOTAL_FILES}},"phase":"delta-core"}' 2>/dev/null || true
+   ```
+   The `echo` line writes a local progress file so the CLI can show progress even when the web UI is not running. Always run BOTH lines.
+5. **Fallback: full-file rewrite** — ONLY if a change hint says "regenerate fully" or changes span more than 50% of the file:
+   ```bash
+   cat > "{{SKILL_DIR}}/FILENAME" << 'LORE_EOF'
+   (full updated content)
+   LORE_EOF
+   ```
+Do NOT read entire files when you only need to edit one section. Grep first, then read the targeted range.
+</tools>
+<installed_skills>
+The user has the following skills already installed and available to the AI agent.
+When applying updates, do NOT add content that duplicates what these skills already
+cover. If a delta introduces a pattern already handled by an installed skill, add a
+brief cross-reference ("For [topic], see the [skill-name] skill.") instead of
+documenting it in full.
+{{INSTALLED_SKILLS_DIGEST}}
+</installed_skills>
+<installed_mcps>
+The user has the following public MCP servers configured. When applying updates,
+if the delta introduces MCP-related patterns for public MCPs listed here, include
+them in the skill documentation. Focus on repo-specific MCP usage patterns.
+{{INSTALLED_MCPS_DIGEST}}
+</installed_mcps>
+<context>
+Repository: {{REPO_NAME}}
+Skill directory: {{SKILL_DIR}}
+<delta_analysis>
+The following analysis describes what changed in the codebase and what needs to be updated in the skill documentation:
+{{DELTA_ANALYSIS}}
+</delta_analysis>
+<change_hints>
+Specific changes to apply per file:
+{{CHANGE_HINTS}}
+</change_hints>
+<clustered_knowledge>
+New conversation knowledge (themes, decisions, patterns from AI coding conversations):
+{{CLUSTERED_KNOWLEDGE}}
+</clustered_knowledge>
+<git_log>
+Recent git activity:
+{{GIT_LOG}}
+</git_log>
+</context>
+<task>
+Apply the changes described in the delta analysis and change hints to the existing skill files.
+This is a TARGETED UPDATE, not a full regeneration.
+Workflow:
+1. **Grep** to locate relevant sections — extract keywords from the change hints and grep across skill files to find which XML sections contain the content that needs updating
+2. **Read** only the targeted section(s) — use line offset/limit based on grep results, not the full file
+3. **Edit** only the changed section(s) using the Edit tool with old_string/new_string
+4. Leave all other sections completely untouched
+5. **Report progress** after editing each file
+6. Repeat for the next file
+For each file listed in the change hints:
+- Grep to find the XML section boundaries and the lines matching the change hint keywords
+- Read only the section that needs editing (use line offset/limit from grep output)
+- Use Edit to replace only that section, preserving everything else
+- Update the `lastUpdated` timestamp in SKILL.md frontmatter to {{TIMESTAMP}}
+Do NOT read entire files when you only need to edit one section. Do NOT rewrite entire files.
+</task>
+<output_format>
+Use the Edit tool for each section that needs changes, then output a summary:
+```
+UPDATED: SKILL.md (2 sections), established-patterns.md (1 section)
+```
+If a change hint says "regenerate fully" for a file, use the Bash heredoc fallback for that file only.
+</output_format>
+<rules>
+- **SKILL DEDUPLICATION**: The `<installed_skills>` section lists skills already available to the agent. Do NOT add content that duplicates what those skills cover. Add cross-references instead ("For [topic], see the [skill-name] skill.").
+- **MCP INTEGRATION**: Public MCPs listed in `<installed_mcps>` that are actively used for this repo should be documented in the skill files. Include the MCP package name, key tools, and how the repo uses them.
+- **GREP FIRST**: Always grep to locate the relevant section before reading or editing. Never read an entire file when you only need one section.
+- **READ TARGETED**: Use the Read tool with line offset/limit to read only the section identified by grep. Only read a full file if the change hints say "regenerate fully."
+- **EDIT IN PLACE**: Use the Edit tool to replace only changed sections. Never rewrite an entire file unless the change hints say "regenerate fully" or changes span more than 50% of the file.
+- **SECTION BOUNDARIES**: Use XML tags (e.g., `<architecture>...</architecture>`) as natural edit boundaries. Replace the full XML section block when its content changed.
+- **SURGICAL UPDATES**: Only modify sections relevant to the delta. Do NOT restructure, rewrite, or rephrase content that hasn't changed.
+- **XML STRUCTURE**: Preserve all existing XML tags. If adding new sections, wrap them in appropriate XML tags.
+- **Frontmatter**: Update `lastUpdated` to "{{TIMESTAMP}}" in SKILL.md. Keep `name` as "{{SKILL_NAME}}".
+- **Preserve quality**: Existing content has been vetted. Only change it when the delta analysis specifically calls for it.
+- **Add, don't replace**: When the delta introduces new patterns, entry points, or conventions, ADD them to the existing lists rather than replacing the lists entirely.
+- **NO DUPLICATION between files**: guidelines.md must NOT duplicate content from established-patterns.md. If adding pattern content, add it to established-patterns.md. guidelines.md should cross-reference: "For [topic] patterns, see [established-patterns.md](established-patterns.md)."
+- **Recent Changes table**: Add a new row at the top of the Recent Changes table describing what this update covers. Use today's date.
+- Replace all {{PLACEHOLDER}} values with actual content.
+- SKILL.md MUST remain under 500 lines. If adding content would exceed this, move details to supporting files.
+- Use imperative form ("Use X" not "You should use X").
+- Concise is key — only add context the agent doesn't already know.
+- **Bash usage**: Use Bash ONLY for `grep` (search), `echo`/`curl` (progress), and the full-file heredoc fallback. Do NOT use Bash for reading files (use Read tool) or for small edits (use Edit tool).
+- **Heredoc delimiter**: When using the fallback, always use `LORE_EOF` (with single quotes to prevent expansion). Never use `EOF` or other common delimiters.
+</rules>

package/prompts/check-relevance.md ADDED Viewed

@@ -0,0 +1,137 @@
+<role>
+You are a technical analyst evaluating whether an AI coding skill needs updating.
+You have access to the Bash tool to inspect specific files or git changes in the repository.
+</role>
+<context>
+Repository: {{REPO_NAME}}
+Repository path: {{REPO_PATH}}
+Last skill update: {{LAST_UPDATED}}
+<existing_skill>
+{{EXISTING_SKILL}}
+</existing_skill>
+<existing_skill_files>
+Files currently in the skill directory:
+{{EXISTING_FILES}}
+</existing_skill_files>
+<clustered_knowledge>
+New conversation knowledge since last scan (themes, decisions, patterns from AI coding conversations):
+{{CLUSTERED_KNOWLEDGE}}
+</clustered_knowledge>
+<git_log>
+Recent commits since last skill update:
+{{GIT_LOG}}
+</git_log>
+<git_diff_stat>
+Files changed since last skill update:
+{{GIT_DIFF_STAT}}
+</git_diff_stat>
+</context>
+<task>
+Analyze the delta (new conversations + git changes) against the existing skill documentation.
+Determine whether the changes are significant enough to warrant updating the skill files.
+If an update IS warranted:
+1. Produce a targeted work plan specifying exactly which files to update and what changes to make.
+2. Produce a detailed delta analysis documenting what changed and why — this analysis will be used
+   directly by the skill writer to apply updates, so it must be thorough and documentation-ready.
+You may use the Bash tool to inspect specific files or git changes in more detail:
+- `git diff <commit>.. -- <file>` to see actual code changes
+- `git show <commit>` to see a specific commit
+- `cat <file>` to read a specific file
+- `git log --oneline -10 -- <path>` to see recent changes to a specific file
+Limit yourself to at most 5-6 tool calls. Focus on the most impactful changes.
+</task>
+<instructions>
+Evaluate the delta using these criteria:
+**Signals that REQUIRE an update (shouldUpdate: true):**
+- New architectural patterns or significant structural changes
+- New modules, entry points, or major components added/removed
+- Convention changes (naming, file organization, code style shifts)
+- Business logic decisions or trade-offs discussed in conversations
+- Migration or technology changes (e.g., state management, framework versions)
+- New dependencies with integration patterns worth documenting
+- Workflow changes (build, test, deploy)
+**Signals that do NOT require an update (shouldUpdate: false):**
+- Typo fixes, formatting changes, comment updates
+- Dependency version bumps without API changes
+- Minor refactors that preserve existing patterns
+- Routine bug fixes without new insights
+- Conversations about debugging without revealing new patterns
+- Test additions that follow existing testing patterns
+- Configuration tweaks without structural impact
+When deciding which files to update, consider:
+- SKILL.md: Update for new entry points, architecture changes, workflow changes
+- established-patterns.md: Update for new patterns, pattern changes, convention shifts
+- guidelines.md: Update for architecture changes, config changes, dependency changes
+- references/*.md: Update only if a specific subsystem was significantly changed
+When confidence is "low", default to shouldUpdate: true (err on the side of freshness).
+**Delta Analysis Guidelines (when shouldUpdate is true):**
+The deltaAnalysis field is critical — it replaces a full research phase and will be passed directly
+to the skill writer. Make it thorough and documentation-ready:
+1. **Code changes**: Describe what changed in the code with specific function/file references.
+   Include short code snippets (5-15 lines) for new patterns or significant changes.
+2. **New patterns/conventions**: Document any new coding patterns, naming conventions, or
+   architectural decisions introduced in the delta.
+3. **Architecture changes**: Describe structural changes — new modules, moved files, changed
+   data flows, new entry points.
+4. **Conversation insights**: Extract actionable insights from conversation knowledge that
+   should be documented (decisions made, trade-offs discussed, rationale for changes).
+5. **Impact summary**: For each file in filesToUpdate, explain specifically what content
+   needs to change and why.
+</instructions>
+<output_format>
+Respond with ONLY a valid JSON object (no markdown fences, no commentary). Schema:
+{
+  "shouldUpdate": boolean,
+  "confidence": "high" | "medium" | "low",
+  "reason": "1-2 sentence explanation",
+  "deltaAnalysis": "Detailed markdown analysis of the delta (see guidelines above). Include code snippets, specific file/function references, and documentation-ready insights. This will be passed directly to the skill writer.",
+  "workPlan": {
+    "filesToUpdate": [
+      {
+        "file": "filename.md",
+        "changeHints": ["Detailed, actionable description of what to change in this file and why"]
+      }
+    ],
+    "filesToSkip": ["file1.md", "file2.md"],
+    "researchFocus": ["Area to investigate in the codebase"]
+  }
+}
+When shouldUpdate is false, omit both deltaAnalysis and workPlan fields entirely.
+When shouldUpdate is true, both deltaAnalysis and workPlan are REQUIRED.
+</output_format>
+<rules>
+- Respond ONLY with valid JSON. No markdown code fences, no preamble, no commentary.
+- The workPlan.filesToUpdate array must only contain files that genuinely need changes.
+- The workPlan.filesToSkip array should list all existing skill files that do NOT need changes.
+- Every file must appear in either filesToUpdate OR filesToSkip — no file should be missing from both.
+- researchFocus should contain 1-5 specific areas/paths in the codebase to investigate.
+- changeHints must be detailed and actionable — include specific section names, function names, and what exactly should be added/modified/removed. Not vague like "update content" but specific like "Add new section documenting the rate-limit handling in invokeWithFallback (src/utils/cli.ts:197-239) which uses exponential backoff with 30s/60s/120s delays".
+- deltaAnalysis must be thorough enough to serve as the sole input for the skill writer — it replaces a full research phase. Include code snippets for new patterns.
+- When in doubt, prefer shouldUpdate: true — it's better to update unnecessarily than to miss important changes.
+- If confidence is "low", set shouldUpdate to true regardless of your analysis.
+</rules>
+</output>