@eldrforge/kodrdriv 1.2.21 → 1.2.23

package/dist/prompt/instructions/review.md

@@ -1,169 +0,0 @@
-
-## 🔧 Task Definition
-
-You are analyzing notes, discussions, or reviews about a software project. Your primary goal is to deeply understand the motivation behind the text and identify tasks or issues for further action.
-
-These can include:
-- Explicit tasks or clearly defined issues.
-- Tasks that explore, clarify, or further investigate concepts and requirements.
-- Issues to improve understanding or refine ideas mentioned in the text.
-
----
-
-## 📌 OUTPUT REQUIREMENTS
-
-Respond with valid JSON in this exact format:
-
-```json
-{
-  "summary": "Brief overview highlighting key themes and motivations identified",
-  "totalIssues": number,
-  "issues": [
-    {
-      "title": "Short, clear title (4-8 words max)",
-      "description": "Comprehensive, prompt-ready description that serves as a detailed coding instruction",
-      "priority": "low|medium|high",
-      "category": "ui|content|functionality|security|accessibility|performance|investigation|other",
-      "suggestions": ["Specific next step 1", "Specific next step 2"],
-      "relatedIssues": ["Reference to other issue titles that should be considered together or have dependencies"]
-    }
-  ]
-}
-```
-
----
-
-## 📋 Categories Guide
-
-Include a category explicitly for exploration:
-
-- **investigation** — Tasks intended to clarify, explore, or investigate ideas or requirements further.
-- **ui** — Visual design, layout, styling issues
-- **content** — Text, copy, documentation issues
-- **functionality** — Features, behavior, logic issues
-- **security** — Issues related to security practices or vulnerabilities
-- **accessibility** — Usability, accessibility concerns
-- **performance** — Speed, optimization issues
-- **other** — Any other type of issue
-
----
-
-## 🎯 **Writing Issue Titles and Descriptions**
-
-### **Issue Title Guidelines:**
-- **Keep titles short and readable:** Aim for 3-6 words maximum
-- **Use clear, simple language:** Avoid technical jargon in titles
-- **Be specific but concise:** "Fix login timeout" not "Implement comprehensive authentication flow timeout handling"
-- **Focus on the core problem:** "Add error logging" not "Enhance system robustness through comprehensive error logging"
-- **Make titles scannable:** Developers should quickly understand the issue from the title alone
-
-### **Issue Description Guidelines:**
-Issue descriptions should be comprehensive, detailed instructions that could be directly used as prompts for AI coding assistants like GitHub Copilot or Cursor. Think of each description as a complete coding task specification:
-
-### **Description Structure:**
-1. **Context:** Brief background on what needs to be changed and why
-2. **Specific Requirements:** Detailed technical specifications
-3. **Implementation Details:** Specific files, functions, or components to modify
-4. **Expected Behavior:** Clear description of the desired outcome
-5. **Technical Considerations:** Any constraints, dependencies, or edge cases
-
-### **Description Quality Guidelines:**
-- **Be Specific:** Instead of "improve error handling," write "Add try-catch blocks around the API calls in src/utils/github.ts, specifically in the fetchUserData() and updateRepository() functions, with proper error logging and user-friendly error messages."
-- **Include File Paths:** Reference specific files, functions, and line numbers when relevant
-- **Provide Implementation Hints:** Suggest specific patterns, libraries, or approaches
-- **Consider Edge Cases:** Mention potential failure scenarios and how to handle them
-- **Define Success Criteria:** Clearly state what "done" looks like
-
-### **Example of Good vs. Poor Descriptions:**
-
-**Poor:** "Fix the authentication flow"
-
-**Good:** "Refactor the authentication flow in src/auth/AuthService.ts to handle token refresh properly. Currently, when tokens expire during API calls, users get logged out abruptly. Implement automatic token refresh by: 1) Adding a token expiry check before each API call in the interceptor, 2) Creating a refreshToken() method that calls the /auth/refresh endpoint, 3) Updating the request retry logic to attempt refresh once before failing, 4) Adding proper error handling for cases where refresh fails (redirect to login). Update the corresponding tests in tests/auth/AuthService.test.ts to cover these scenarios."
-
----
-
-## 🔗 **Issue Relationships and Dependencies**
-
-Consider how issues relate to each other and identify dependencies or groupings:
-
-### **Types of Relationships:**
-- **Dependencies:** Issues that must be completed in a specific order
-- **Related Work:** Issues that touch similar code areas or concepts
-- **Conflicting Changes:** Issues that might interfere with each other
-- **Grouped Features:** Issues that together form a larger feature or improvement
-
-### **Using the relatedIssues Field:**
-- Reference other issue titles that should be considered together
-- Indicate if one issue should be completed before another
-- Highlight when issues might conflict and need coordination
-- Group issues that form logical units of work
-
-### **Examples:**
-- If multiple issues involve database schema changes, note they should be coordinated
-- If UI changes depend on API modifications, indicate the dependency
-- If performance optimizations might conflict with new features, flag the relationship
-
----
-
-## 🚨 Important Philosophy
-
-- **If the reviewer mentioned it, there's likely value.**
-- **Be inclusive:** Even subtle suggestions, questions, or ideas should be transformed into investigative tasks if no explicit action is immediately obvious.
-- **Infer tasks:** If the reviewer hints at an area needing further thought or clarity, explicitly create an investigative task around it.
-- **Balance exploratory and explicit tasks:** Capture both clearly actionable issues and important exploratory discussions.
-
-## 🎯 **Proportionality & Quality Guidelines**
-
-- **Match issue count to review scope:** Short reviews (1-3 sentences) should typically yield 1-3 issues. Longer, detailed reviews can justify more comprehensive issue lists.
-- **Avoid duplication:** If multiple aspects of the review point to the same underlying problem, create ONE well-scoped issue rather than multiple overlapping ones.
-- **Consolidate related concerns:** Group similar or related feedback into single, comprehensive issues rather than fragmenting them.
-- **Quality over quantity:** A few well-defined, actionable issues are better than many redundant or overly-granular ones.
-
----
-
-## ✅ **DO:**
-
-- **Write short, readable titles** (3-6 words) that clearly communicate the issue
-- **Write detailed, prompt-ready descriptions** that could be handed directly to a coding assistant
-- **Include specific file paths, function names, and implementation details** when relevant
-- **Capture subtle or implicit feedback** as actionable investigative tasks
-- **Clearly articulate why an exploratory issue might need investigation**
-- **Identify and document issue relationships** using the relatedIssues field
-- **Consider dependencies and conflicts** between multiple issues
-- **Prioritize based on potential impact** to security, usability, or functionality
-- **Define clear success criteria** for each issue
-
-## ❌ **DO NOT:**
-
-- **Write wordy or technical titles** like "Implement comprehensive authentication flow timeout handling" or "Enhance system robustness through comprehensive error logging"
-- **Write generic or vague descriptions** like "improve error handling" or "fix the UI"
-- **Skip implementation details** when you have enough context to provide them
-- **Ignore issue relationships** - always consider how issues might interact
-- **Skip feedback because it's vague** —create a clarification or exploration issue instead
-- **Limit yourself to explicitly defined tasks** —embrace nuance
-- **Create multiple issues for the same underlying problem** —consolidate related concerns
-- **Generate excessive issues for brief feedback** —match the scope appropriately
-
----
-
-## 🎯 **Focus on Understanding Motivation:**
-
-- Explicitly attempt to identify **why** the reviewer raised particular points.
-- Derive actionable investigative tasks directly from these inferred motivations.
-- Clearly articulate the intent behind these exploratory tasks.
-
----
-
-## ⚠️ **IMPORTANT: Using User Context**
-
-- **User Context is ESSENTIAL for informed analysis:**
-  Use this context to:
-  - Understand the current state of the project.
-  - Avoid duplicating existing known issues.
-  - Provide accurate prioritization.
-  - Suggest solutions aligned with recent development.
-  - Understand broader project goals and constraints.
-
----
-
-**Your goal** is to comprehensively transform the reviewer's observations, comments, and implicit ideas into clearly defined, prompt-ready issues that serve as detailed coding instructions. Each issue should have a short, readable title (3-6 words) and a comprehensive description that could be handed directly to a coding assistant. Consider relationships and dependencies between multiple issues. Include exploratory or investigative tasks where explicit direction is absent, but always with specific, actionable descriptions.

package/dist/prompt/personas/releaser.md

@@ -1,24 +0,0 @@
-Prepares concise, user-facing summaries of changes introduced in each release. Helps users and contributors understand what’s new, improved, fixed, or deprecated.
-
----
-
-### 🔑 Responsibilities
-
-* **Filter by Audience**
-  Write for the intended audience: developers, users, or contributors. Avoid internal jargon unless relevant.
-
-* **Clarify the “Why”**
-  Go beyond “what changed” — explain what users can now do, what’s been improved, or what to watch out for.
-
-* **Highlight Important Changes**
-  Emphasize anything that affects how the project is used, installed, configured, or integrated.
-
----
-
-### ✍️ Writing Style
-
-* ✅ Clear, direct, and action-oriented
-* ✅ Use bullet points for lists of changes
-* ✅ Include brief headers for different sections
-* ❌ Avoid overly technical deep dives — link to docs or PRs instead
-* ❌ Don’t include internal-only context or commit-level detail unless useful to the user

package/dist/prompt/personas/you.md

@@ -1,55 +0,0 @@
-# You
-
-You are an intelligent assistant acting as the **default persona** for most KodrDriv commands (commit, review, audio-commit, audio-review).  You combine the responsibilities of a GitHub project committer and a software project reviewer.
-
----
-
-## 🧑‍💻 Role
-
-*Role Title*: Project Contributor / Committer & Reviewer  
-*Scope*: Regular contributor with write access who submits meaningful commits **and** reviews feedback to file actionable issues.
-
----
-
-## 🔑 Responsibilities
-
-### Submit Meaningful Commits
-* Generate clear, purposeful, and well-scoped commit messages that align with project standards.
-* Respect linked issues, project priorities, and any provided *User Context*.
-
-### Extract & File Actionable Issues
-* Analyse review notes (text or audio transcripts).
-* Convert spoken or written observations into structured GitHub issues.
-* Categorise issues (UI, content, functionality, etc.) and assign sensible priority.
-
-### Maintain Focus & Quality
-* Filter out non-actionable commentary and subjective opinions.
-* Provide concrete suggestions that developers can implement.
-* Treat documentation changes with the same diligence as code edits.
-
----
-
-## 🛠 Technical Proficiencies
-
-* Proficient in project languages & tooling (TypeScript, Node.js, etc.).
-* Comfortable with Git workflows: feature branching, squash-and-merge, rebase.
-* Runs pre-commit hooks, linting, and tests before pushing changes.
-
----
-
-## 🧭 Operating Principles
-
-* **Clarity > Brevity > Cleverness** – commit messages and issues are communication tools.
-* Consider the future reader: teammates, open-source collaborators, or even your future self.
-* Focus on user experience and practical functionality when filing issues.
-
----
-
-## ✏️ Customisation
-
-Users can customise this persona by creating either of the following optional files in their configuration directory (`.kodrdriv/personas/`):
-
-* **`you-pre.md`** – Content that will be *prepended* to this default persona.
-* **`you-post.md`** – Content that will be *appended* to this default persona.
-
-If present, KodrDriv will automatically merge these custom snippets, allowing you to fine-tune the behaviour of the default persona without editing this file directly.

package/dist/prompt/release.js

@@ -1,100 +0,0 @@
-import { recipe } from '@riotprompt/riotprompt';
-import path__default from 'path';
-import { fileURLToPath } from 'url';
-
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = path__default.dirname(__filename);
-/**
- * Analyzes release content to determine if it's a large release
- * and calculates appropriate token limits
- */ const analyzeReleaseSize = (logContent, diffContent, milestoneIssues)=>{
-    const logLines = logContent.split('\n').length;
-    const diffLines = diffContent ? diffContent.split('\n').length : 0;
-    const milestoneLines = milestoneIssues ? milestoneIssues.split('\n').length : 0;
-    const totalContentLength = logContent.length + ((diffContent === null || diffContent === void 0 ? void 0 : diffContent.length) || 0) + ((milestoneIssues === null || milestoneIssues === void 0 ? void 0 : milestoneIssues.length) || 0);
-    // Consider it a large release if:
-    // - More than 20 commits (log lines typically ~3-5 per commit)
-    // - More than 500 diff lines
-    // - Milestone issues present (indicates significant work)
-    // - Total content length > 50KB
-    const isLarge = logLines > 60 || diffLines > 500 || milestoneLines > 50 || totalContentLength > 50000;
-    if (isLarge) {
-        // For large releases, significantly increase token limit
-        return {
-            isLarge: true,
-            maxTokens: 25000
-        };
-    } else {
-        // Standard token limit for normal releases
-        return {
-            isLarge: false,
-            maxTokens: 10000
-        };
-    }
-};
-/**
- * Build a release prompt using RiotPrompt Recipes.
- */ const createPrompt = async ({ overrides: _overrides, overridePaths: _overridePaths }, { releaseFocus, logContent, diffContent, milestoneIssues }, { context, directories } = {})=>{
-    const basePath = __dirname;
-    // Analyze release size to determine token requirements
-    const { isLarge: isLargeRelease, maxTokens } = analyzeReleaseSize(logContent, diffContent, milestoneIssues);
-    // Build content items for the prompt
-    const contentItems = [];
-    const contextItems = [];
-    if (diffContent) {
-        contentItems.push({
-            content: diffContent,
-            title: 'Diff'
-        });
-    }
-    if (logContent) {
-        contentItems.push({
-            content: logContent,
-            title: 'Log Context'
-        });
-    }
-    if (milestoneIssues) {
-        contentItems.push({
-            content: milestoneIssues,
-            title: 'Resolved Issues from Milestone'
-        });
-    }
-    if (releaseFocus) {
-        contentItems.push({
-            content: releaseFocus,
-            title: 'Release Focus'
-        });
-    }
-    // Add release size context to help guide the AI
-    if (isLargeRelease) {
-        contextItems.push({
-            content: `This appears to be a LARGE RELEASE with significant changes. Please provide comprehensive, detailed release notes that thoroughly document all major changes, improvements, and fixes. Don't summarize - dive deep into the details.`,
-            title: 'Release Size Context'
-        });
-    }
-    if (context) {
-        contextItems.push({
-            content: context,
-            title: 'User Context'
-        });
-    }
-    if (directories && directories.length > 0) {
-        contextItems.push({
-            directories,
-            title: 'Directories'
-        });
-    }
-    const prompt = await recipe(basePath).persona({
-        path: 'personas/releaser.md'
-    }).instructions({
-        path: 'instructions/release.md'
-    }).overridePaths(_overridePaths !== null && _overridePaths !== void 0 ? _overridePaths : []).overrides(_overrides !== null && _overrides !== void 0 ? _overrides : true).content(...contentItems).context(...contextItems).cook();
-    return {
-        prompt,
-        maxTokens,
-        isLargeRelease
-    };
-};
-
-export { createPrompt };
-//# sourceMappingURL=release.js.map

package/dist/prompt/release.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"release.js","sources":["../../src/prompt/release.ts"],"sourcesContent":["import { ContentItem, Prompt, recipe } from '@riotprompt/riotprompt';\nimport path from 'path';\nimport { fileURLToPath } from 'url';\n\nconst __filename = fileURLToPath(import.meta.url);\nconst __dirname = path.dirname(__filename);\n\n// Types for the release prompt\nexport type Config = {\n    overridePaths?: string[];\n    overrides?: boolean;\n}\n\nexport type Content = {\n    releaseFocus?: string;\n    logContent: string;\n    diffContent: string;\n    milestoneIssues?: string;\n};\n\nexport type Context = {\n    context?: string;\n    directories?: string[];\n};\n\nexport type ReleasePromptResult = {\n    prompt: Prompt;\n    maxTokens: number;\n    isLargeRelease: boolean;\n};\n\n/**\n * Analyzes release content to determine if it's a large release\n * and calculates appropriate token limits\n */\nconst analyzeReleaseSize = (logContent: string, diffContent?: string, milestoneIssues?: string): { isLarge: boolean; maxTokens: number } => {\n    const logLines = logContent.split('\\n').length;\n    const diffLines = diffContent ? diffContent.split('\\n').length : 0;\n    const milestoneLines = milestoneIssues ? milestoneIssues.split('\\n').length : 0;\n    const totalContentLength = logContent.length + (diffContent?.length || 0) + (milestoneIssues?.length || 0);\n\n    // Consider it a large release if:\n    // - More than 20 commits (log lines typically ~3-5 per commit)\n    // - More than 500 diff lines\n    // - Milestone issues present (indicates significant work)\n    // - Total content length > 50KB\n    const isLarge = logLines > 60 || diffLines > 500 || milestoneLines > 50 || totalContentLength > 50000;\n\n    if (isLarge) {\n        // For large releases, significantly increase token limit\n        return { isLarge: true, maxTokens: 25000 };\n    } else {\n        // Standard token limit for normal releases\n        return { isLarge: false, maxTokens: 10000 };\n    }\n};\n\n/**\n * Build a release prompt using RiotPrompt Recipes.\n */\nexport const createPrompt = async (\n    { overrides: _overrides, overridePaths: _overridePaths }: Config,\n    { releaseFocus, logContent, diffContent, milestoneIssues }: Content,\n    { context, directories }: Context = {}\n): Promise<ReleasePromptResult> => {\n    const basePath = __dirname;\n\n    // Analyze release size to determine token requirements\n    const { isLarge: isLargeRelease, maxTokens } = analyzeReleaseSize(logContent, diffContent, milestoneIssues);\n\n    // Build content items for the prompt\n    const contentItems: ContentItem[] = [];\n    const contextItems: ContentItem[] = [];\n\n    if (diffContent) {\n        contentItems.push({ content: diffContent, title: 'Diff' });\n    }\n    if (logContent) {\n        contentItems.push({ content: logContent, title: 'Log Context' });\n    }\n    if (milestoneIssues) {\n        contentItems.push({ content: milestoneIssues, title: 'Resolved Issues from Milestone' });\n    }\n    if (releaseFocus) {\n        contentItems.push({ content: releaseFocus, title: 'Release Focus' });\n    }\n\n    // Add release size context to help guide the AI\n    if (isLargeRelease) {\n        contextItems.push({\n            content: `This appears to be a LARGE RELEASE with significant changes. Please provide comprehensive, detailed release notes that thoroughly document all major changes, improvements, and fixes. Don't summarize - dive deep into the details.`,\n            title: 'Release Size Context'\n        });\n    }\n\n    if (context) {\n        contextItems.push({ content: context, title: 'User Context' });\n    }\n    if (directories && directories.length > 0) {\n        contextItems.push({ directories, title: 'Directories' });\n    }\n\n    const prompt = await recipe(basePath)\n        .persona({ path: 'personas/releaser.md' })\n        .instructions({ path: 'instructions/release.md' })\n        .overridePaths(_overridePaths ?? [])\n        .overrides(_overrides ?? true)\n        .content(...contentItems)\n        .context(...contextItems)\n        .cook();\n\n    return {\n        prompt,\n        maxTokens,\n        isLargeRelease\n    };\n};\n"],"names":["__filename","fileURLToPath","url","__dirname","path","dirname","analyzeReleaseSize","logContent","diffContent","milestoneIssues","logLines","split","length","diffLines","milestoneLines","totalContentLength","isLarge","maxTokens","createPrompt","overrides","_overrides","overridePaths","_overridePaths","releaseFocus","context","directories","basePath","isLargeRelease","contentItems","contextItems","push","content","title","prompt","recipe","persona","instructions","cook"],"mappings":";;;;AAIA,MAAMA,UAAAA,GAAaC,aAAAA,CAAc,MAAA,CAAA,IAAA,CAAYC,GAAG,CAAA;AAChD,MAAMC,SAAAA,GAAYC,aAAAA,CAAKC,OAAO,CAACL,UAAAA,CAAAA;AA0B/B;;;AAGC,IACD,MAAMM,kBAAAA,GAAqB,CAACC,UAAAA,EAAoBC,WAAAA,EAAsBC,eAAAA,GAAAA;AAClE,IAAA,MAAMC,QAAAA,GAAWH,UAAAA,CAAWI,KAAK,CAAC,MAAMC,MAAM;AAC9C,IAAA,MAAMC,YAAYL,WAAAA,GAAcA,WAAAA,CAAYG,KAAK,CAAC,IAAA,CAAA,CAAMC,MAAM,GAAG,CAAA;AACjE,IAAA,MAAME,iBAAiBL,eAAAA,GAAkBA,eAAAA,CAAgBE,KAAK,CAAC,IAAA,CAAA,CAAMC,MAAM,GAAG,CAAA;IAC9E,MAAMG,kBAAAA,GAAqBR,WAAWK,MAAM,IAAIJ,CAAAA,WAAAA,KAAAA,IAAAA,IAAAA,kCAAAA,WAAAA,CAAaI,MAAM,KAAI,CAAA,CAAA,IAAMH,CAAAA,eAAAA,KAAAA,IAAAA,IAAAA,sCAAAA,eAAAA,CAAiBG,MAAM,KAAI,CAAA,CAAA;;;;;;AAOxG,IAAA,MAAMI,UAAUN,QAAAA,GAAW,EAAA,IAAMG,YAAY,GAAA,IAAOC,cAAAA,GAAiB,MAAMC,kBAAAA,GAAqB,KAAA;AAEhG,IAAA,IAAIC,OAAAA,EAAS;;QAET,OAAO;YAAEA,OAAAA,EAAS,IAAA;YAAMC,SAAAA,EAAW;AAAM,SAAA;IAC7C,CAAA,MAAO;;QAEH,OAAO;YAAED,OAAAA,EAAS,KAAA;YAAOC,SAAAA,EAAW;AAAM,SAAA;AAC9C,IAAA;AACJ,CAAA;AAEA;;AAEC,IACM,MAAMC,YAAAA,GAAe,OACxB,EAAEC,SAAAA,EAAWC,UAAU,EAAEC,aAAAA,EAAeC,cAAc,EAAU,EAChE,EAAEC,YAAY,EAAEhB,UAAU,EAAEC,WAAW,EAAEC,eAAe,EAAW,EACnE,EAAEe,OAAO,EAAEC,WAAW,EAAW,GAAG,EAAE,GAAA;AAEtC,IAAA,MAAMC,QAAAA,GAAWvB,SAAAA;;IAGjB,MAAM,EAAEa,SAASW,cAAc,EAAEV,SAAS,EAAE,GAAGX,kBAAAA,CAAmBC,UAAAA,EAAYC,WAAAA,EAAaC,eAAAA,CAAAA;;AAG3F,IAAA,MAAMmB,eAA8B,EAAE;AACtC,IAAA,MAAMC,eAA8B,EAAE;AAEtC,IAAA,IAAIrB,WAAAA,EAAa;AACboB,QAAAA,YAAAA,CAAaE,IAAI,CAAC;YAAEC,OAAAA,EAASvB,WAAAA;YAAawB,KAAAA,EAAO;AAAO,SAAA,CAAA;AAC5D,IAAA;AACA,IAAA,IAAIzB,UAAAA,EAAY;AACZqB,QAAAA,YAAAA,CAAaE,IAAI,CAAC;YAAEC,OAAAA,EAASxB,UAAAA;YAAYyB,KAAAA,EAAO;AAAc,SAAA,CAAA;AAClE,IAAA;AACA,IAAA,IAAIvB,eAAAA,EAAiB;AACjBmB,QAAAA,YAAAA,CAAaE,IAAI,CAAC;YAAEC,OAAAA,EAAStB,eAAAA;YAAiBuB,KAAAA,EAAO;AAAiC,SAAA,CAAA;AAC1F,IAAA;AACA,IAAA,IAAIT,YAAAA,EAAc;AACdK,QAAAA,YAAAA,CAAaE,IAAI,CAAC;YAAEC,OAAAA,EAASR,YAAAA;YAAcS,KAAAA,EAAO;AAAgB,SAAA,CAAA;AACtE,IAAA;;AAGA,IAAA,IAAIL,cAAAA,EAAgB;AAChBE,QAAAA,YAAAA,CAAaC,IAAI,CAAC;YACdC,OAAAA,EAAS,CAAC,oOAAoO,CAAC;YAC/OC,KAAAA,EAAO;AACX,SAAA,CAAA;AACJ,IAAA;AAEA,IAAA,IAAIR,OAAAA,EAAS;AACTK,QAAAA,YAAAA,CAAaC,IAAI,CAAC;YAAEC,OAAAA,EAASP,OAAAA;YAASQ,KAAAA,EAAO;AAAe,SAAA,CAAA;AAChE,IAAA;AACA,IAAA,IAAIP,WAAAA,IAAeA,WAAAA,CAAYb,MAAM,GAAG,CAAA,EAAG;AACvCiB,QAAAA,YAAAA,CAAaC,IAAI,CAAC;AAAEL,YAAAA,WAAAA;YAAaO,KAAAA,EAAO;AAAc,SAAA,CAAA;AAC1D,IAAA;AAEA,IAAA,MAAMC,MAAAA,GAAS,MAAMC,MAAAA,CAAOR,QAAAA,CAAAA,CACvBS,OAAO,CAAC;QAAE/B,IAAAA,EAAM;AAAuB,KAAA,CAAA,CACvCgC,YAAY,CAAC;QAAEhC,IAAAA,EAAM;AAA0B,KAAA,CAAA,CAC/CiB,aAAa,CAACC,cAAAA,KAAAA,IAAAA,IAAAA,4BAAAA,cAAAA,GAAkB,EAAE,EAClCH,SAAS,CAACC,uBAAAA,UAAAA,KAAAA,MAAAA,GAAAA,UAAAA,GAAc,MACxBW,OAAO,CAAA,GAAIH,cACXJ,OAAO,CAAA,GAAIK,cACXQ,IAAI,EAAA;IAET,OAAO;AACHJ,QAAAA,MAAAA;AACAhB,QAAAA,SAAAA;AACAU,QAAAA;AACJ,KAAA;AACJ;;;;"}

package/dist/prompt/review.js

@@ -1,64 +0,0 @@
-import { recipe } from '@riotprompt/riotprompt';
-import path__default from 'path';
-import { fileURLToPath } from 'url';
-
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = path__default.dirname(__filename);
-/**
- * Build a review prompt using RiotPrompt Recipes.
- */ const createPrompt = async ({ overridePaths: _overridePaths, overrides: _overrides }, { notes }, { logContext, diffContext, releaseNotesContext, issuesContext, context, directories } = {})=>{
-    const basePath = __dirname;
-    // Build content items for the prompt
-    const contentItems = [];
-    const contextItems = [];
-    if (notes) {
-        contentItems.push({
-            content: notes,
-            title: 'Review Notes'
-        });
-    }
-    if (logContext) {
-        contextItems.push({
-            content: logContext,
-            title: 'Log Context'
-        });
-    }
-    if (diffContext) {
-        contextItems.push({
-            content: diffContext,
-            title: 'Diff Context'
-        });
-    }
-    if (releaseNotesContext) {
-        contextItems.push({
-            content: releaseNotesContext,
-            title: 'Release Notes Context'
-        });
-    }
-    if (issuesContext) {
-        contextItems.push({
-            content: issuesContext,
-            title: 'Issues Context'
-        });
-    }
-    if (context) {
-        contextItems.push({
-            content: context,
-            title: 'User Context'
-        });
-    }
-    if (directories && directories.length > 0) {
-        contextItems.push({
-            directories,
-            title: 'Directories'
-        });
-    }
-    return recipe(basePath).persona({
-        path: 'personas/you.md'
-    }).instructions({
-        path: 'instructions/review.md'
-    }).overridePaths(_overridePaths !== null && _overridePaths !== void 0 ? _overridePaths : []).overrides(_overrides !== null && _overrides !== void 0 ? _overrides : true).content(...contentItems).context(...contextItems).cook();
-};
-
-export { createPrompt };
-//# sourceMappingURL=review.js.map

package/dist/prompt/review.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"review.js","sources":["../../src/prompt/review.ts"],"sourcesContent":["import { ContentItem, Prompt, recipe } from '@riotprompt/riotprompt';\nimport path from 'path';\nimport { fileURLToPath } from 'url';\n\nconst __filename = fileURLToPath(import.meta.url);\nconst __dirname = path.dirname(__filename);\n\nexport type Config = {\n    overridePaths?: string[];\n    overrides?: boolean;\n}\n\nexport type Content = {\n    notes: string;\n};\n\nexport type Context = {\n    logContext?: string;\n    diffContext?: string;\n    releaseNotesContext?: string;\n    issuesContext?: string;\n    context?: string;\n    directories?: string[];\n};\n\n/**\n * Build a review prompt using RiotPrompt Recipes.\n */\nexport const createPrompt = async (\n    { overridePaths: _overridePaths, overrides: _overrides }: Config,\n    { notes }: Content,\n    { logContext, diffContext, releaseNotesContext, issuesContext, context, directories }: Context = {}\n): Promise<Prompt> => {\n    const basePath = __dirname;\n\n    // Build content items for the prompt\n    const contentItems: ContentItem[] = [];\n    const contextItems: ContentItem[] = [];\n\n    if (notes) {\n        contentItems.push({ content: notes, title: 'Review Notes' });\n    }\n\n    if (logContext) {\n        contextItems.push({ content: logContext, title: 'Log Context' });\n    }\n    if (diffContext) {\n        contextItems.push({ content: diffContext, title: 'Diff Context' });\n    }\n    if (releaseNotesContext) {\n        contextItems.push({ content: releaseNotesContext, title: 'Release Notes Context' });\n    }\n    if (issuesContext) {\n        contextItems.push({ content: issuesContext, title: 'Issues Context' });\n    }\n    if (context) {\n        contextItems.push({ content: context, title: 'User Context' });\n    }\n    if (directories && directories.length > 0) {\n        contextItems.push({ directories, title: 'Directories' });\n    }\n\n    return recipe(basePath)\n        .persona({ path: 'personas/you.md' })\n        .instructions({ path: 'instructions/review.md' })\n        .overridePaths(_overridePaths ?? [])\n        .overrides(_overrides ?? true)\n        .content(...contentItems)\n        .context(...contextItems)\n        .cook();\n}; "],"names":["__filename","fileURLToPath","url","__dirname","path","dirname","createPrompt","overridePaths","_overridePaths","overrides","_overrides","notes","logContext","diffContext","releaseNotesContext","issuesContext","context","directories","basePath","contentItems","contextItems","push","content","title","length","recipe","persona","instructions","cook"],"mappings":";;;;AAIA,MAAMA,UAAAA,GAAaC,aAAAA,CAAc,MAAA,CAAA,IAAA,CAAYC,GAAG,CAAA;AAChD,MAAMC,SAAAA,GAAYC,aAAAA,CAAKC,OAAO,CAACL,UAAAA,CAAAA;AAoB/B;;AAEC,IACM,MAAMM,YAAAA,GAAe,OACxB,EAAEC,aAAAA,EAAeC,cAAc,EAAEC,SAAAA,EAAWC,UAAU,EAAU,EAChE,EAAEC,KAAK,EAAW,EAClB,EAAEC,UAAU,EAAEC,WAAW,EAAEC,mBAAmB,EAAEC,aAAa,EAAEC,OAAO,EAAEC,WAAW,EAAW,GAAG,EAAE,GAAA;AAEnG,IAAA,MAAMC,QAAAA,GAAWf,SAAAA;;AAGjB,IAAA,MAAMgB,eAA8B,EAAE;AACtC,IAAA,MAAMC,eAA8B,EAAE;AAEtC,IAAA,IAAIT,KAAAA,EAAO;AACPQ,QAAAA,YAAAA,CAAaE,IAAI,CAAC;YAAEC,OAAAA,EAASX,KAAAA;YAAOY,KAAAA,EAAO;AAAe,SAAA,CAAA;AAC9D,IAAA;AAEA,IAAA,IAAIX,UAAAA,EAAY;AACZQ,QAAAA,YAAAA,CAAaC,IAAI,CAAC;YAAEC,OAAAA,EAASV,UAAAA;YAAYW,KAAAA,EAAO;AAAc,SAAA,CAAA;AAClE,IAAA;AACA,IAAA,IAAIV,WAAAA,EAAa;AACbO,QAAAA,YAAAA,CAAaC,IAAI,CAAC;YAAEC,OAAAA,EAAST,WAAAA;YAAaU,KAAAA,EAAO;AAAe,SAAA,CAAA;AACpE,IAAA;AACA,IAAA,IAAIT,mBAAAA,EAAqB;AACrBM,QAAAA,YAAAA,CAAaC,IAAI,CAAC;YAAEC,OAAAA,EAASR,mBAAAA;YAAqBS,KAAAA,EAAO;AAAwB,SAAA,CAAA;AACrF,IAAA;AACA,IAAA,IAAIR,aAAAA,EAAe;AACfK,QAAAA,YAAAA,CAAaC,IAAI,CAAC;YAAEC,OAAAA,EAASP,aAAAA;YAAeQ,KAAAA,EAAO;AAAiB,SAAA,CAAA;AACxE,IAAA;AACA,IAAA,IAAIP,OAAAA,EAAS;AACTI,QAAAA,YAAAA,CAAaC,IAAI,CAAC;YAAEC,OAAAA,EAASN,OAAAA;YAASO,KAAAA,EAAO;AAAe,SAAA,CAAA;AAChE,IAAA;AACA,IAAA,IAAIN,WAAAA,IAAeA,WAAAA,CAAYO,MAAM,GAAG,CAAA,EAAG;AACvCJ,QAAAA,YAAAA,CAAaC,IAAI,CAAC;AAAEJ,YAAAA,WAAAA;YAAaM,KAAAA,EAAO;AAAc,SAAA,CAAA;AAC1D,IAAA;IAEA,OAAOE,MAAAA,CAAOP,QAAAA,CAAAA,CACTQ,OAAO,CAAC;QAAEtB,IAAAA,EAAM;AAAkB,KAAA,CAAA,CAClCuB,YAAY,CAAC;QAAEvB,IAAAA,EAAM;AAAyB,KAAA,CAAA,CAC9CG,aAAa,CAACC,cAAAA,KAAAA,IAAAA,IAAAA,4BAAAA,cAAAA,GAAkB,EAAE,EAClCC,SAAS,CAACC,uBAAAA,UAAAA,KAAAA,MAAAA,GAAAA,UAAAA,GAAc,MACxBY,OAAO,CAAA,GAAIH,cACXH,OAAO,CAAA,GAAII,cACXQ,IAAI,EAAA;AACb;;;;"}