@voidwire/llm-summarize 3.1.0 → 3.3.0

package/index.ts

@@ -46,6 +46,8 @@ export interface SummarizeOptions {
   model?: string;
   maxTokens?: number;
   mode?: "quick" | "insights";
+  /** User name to include in summary (e.g., "Rudy") */
+  userName?: string;
 }
 
 export type ProviderType = "anthropic" | "openai" | "ollama";
@@ -56,45 +58,77 @@ export type SummarizeMode = "quick" | "insights";
 // ============================================================================
 
 /**
- * Quick mode: Fast one-liner summary for user prompts
+ * Build quick mode prompt with optional user name
  */
-const QUICK_PROMPT = `Summarize what the user is asking or doing in one sentence.
-Use the user's name from the context in your summary (e.g., "Rudy asked about...").
+function buildQuickPrompt(userName?: string): string {
+  const nameInstruction = userName ? `Start with "${userName}".` : "";
 
+  return `Summarize what the user is asking or doing in one sentence.
+${nameInstruction}
 Output JSON only: {"summary": "One sentence summary"}`;
+}
 
 /**
- * Insights mode: Full SessionInsights extraction for responses
+ * Build insights mode prompt for session insight extraction
+ * Note: userName param kept for API compatibility but not used in insights mode
  */
-const INSIGHTS_PROMPT = `You are an experienced engineering manager reviewing session transcripts to extract actionable team insights.
+function buildInsightsPrompt(_userName?: string): string {
+  return `You are a senior engineering manager extracting reusable insights from development sessions.
+
+You receive transcripts with clear role markers:
+- "User Asked:" = the human directing work (requests, approves, provides context)
+- "Assistant Response:" = the AI executing work (implements, builds, debugs, explains)
 
-Analyze the development session conversation and extract structured observations.
+Your job: extract what's worth remembering for future sessions.
 
 <output_schema>
 {
-  "summary": "One sentence: what was accomplished or decided",
-  "decisions": ["Specific decision and its reasoning"],
-  "patterns_used": ["Development pattern or approach observed"],
-  "preferences_expressed": ["User preference revealed through actions or statements"],
-  "problems_solved": ["Problem that was addressed and how"],
-  "tools_heavy": ["Tool used repeatedly or in notable ways"]
+  "summary": "One sentence capturing what was accomplished and how",
+  "decisions": ["Decision made with reasoning and trade-offs considered"],
+  "patterns_used": ["Development pattern or approach, with context on why it was chosen"],
+  "preferences_expressed": ["Preference revealed through direction or feedback"],
+  "problems_solved": ["Problem encountered and the specific solution applied"],
+  "tools_heavy": ["Tool used repeatedly or for critical work"]
 }
 </output_schema>
 
+<attribution_rules>
+- User actions: requested, approved, directed, provided, chose, preferred
+- Assistant actions: implemented, built, debugged, refactored, created, fixed
+- Never say "User implemented" or "User built" — users direct, assistants execute
+</attribution_rules>
+
+<quality_guidance>
+Extract specifics with context, not bare facts:
+
+SPARSE (avoid):
+- "Made a database decision"
+- "Fixed a bug"
+- "Used TypeScript"
+
+RICH (prefer):
+- "Chose SQLite over Postgres for single-user CLI tool — avoids server dependency"
+- "Fixed race condition in webhook handler by adding mutex lock — was causing duplicate events"
+- "Used Zod for runtime validation at API boundary — catches malformed input before it hits business logic"
+</quality_guidance>
+
 <rules>
-- Use the user's name from the context in the summary field (e.g., "Rudy implemented...")
-- Include a field ONLY when the conversation provides clear evidence
-- Extract specifics: "Chose SQLite over Postgres for single-user simplicity" not "Made a database decision"
+- Include a field ONLY when the transcript provides clear evidence
 - Omit empty arrays entirely
+- Capture the "why" when present — reasoning is more valuable than the decision alone
+- Technical specifics (library names, patterns, trade-offs) make insights reusable
 </rules>
 
 Output valid JSON only. No markdown code blocks, no explanation.`;
+}
 
 /**
  * Get prompt for the specified mode
  */
-function getPromptForMode(mode: SummarizeMode): string {
-  return mode === "quick" ? QUICK_PROMPT : INSIGHTS_PROMPT;
+function getPromptForMode(mode: SummarizeMode, userName?: string): string {
+  return mode === "quick"
+    ? buildQuickPrompt(userName)
+    : buildInsightsPrompt(userName);
 }
 
 // ============================================================================
@@ -494,7 +528,8 @@ export async function summarize(
   const maxTokens = options?.maxTokens || config.maxTokens;
   const apiKey = config.apiKey;
   const mode: SummarizeMode = options?.mode || "insights";
-  const systemPrompt = getPromptForMode(mode);
+  const userName = options?.userName;
+  const systemPrompt = getPromptForMode(mode, userName);
 
   // Validate config
   if (!provider) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@voidwire/llm-summarize",
-  "version": "3.1.0",
+  "version": "3.3.0",
   "description": "Structured session insight extraction for knowledge systems",
   "type": "module",
   "main": "./index.ts",
@@ -18,9 +18,6 @@
     "README.md",
     "LICENSE"
   ],
-  "scripts": {
-    "test": "bun test"
-  },
   "keywords": [
     "llm",
     "summarize",
@@ -42,5 +39,8 @@
   },
   "engines": {
     "bun": ">=1.0.0"
+  },
+  "scripts": {
+    "test": "bun test"
   }
-}
+}