@voidwire/llm-summarize 3.5.0 → 3.7.0

package/index.ts

@@ -36,7 +36,6 @@ export interface SessionInsights {
   patterns_used?: string[];
   preferences_expressed?: string[];
   problems_solved?: string[];
-  tools_heavy?: string[];
 }
 
 export interface SummarizeResult {
@@ -146,55 +145,57 @@ Output valid JSON only. No markdown, no explanation.`;
  * Note: userName param kept for API compatibility but not used in insights mode
  */
 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)
-
-Your job: extract what's worth remembering for future sessions.
-
-<output_schema>
-{
-  "summary": "One sentence capturing what was accomplished and how",
-  "current_focus": "What work is actively in progress — the specific task, feature, or thread (omit if session was exploratory with no clear focus)",
-  "next_steps": ["What should happen when work resumes — concrete actions, not vague intentions"],
-  "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>
-- 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.`;
+  return `You are a session state extractor. Given a development conversation, produce a JSON snapshot of the session's current state.
+
+<instructions>
+1. Read the conversation in the <transcript> section
+2. Ignore the <previous_state> section — it is background context only, not part of this session
+3. Extract ONLY what happened in the transcript
+4. Produce a JSON object with the fields described below
+</instructions>
+
+<fields>
+- summary: One sentence describing what was accomplished this session
+- current_focus: The specific task or feature being worked on (omit if exploratory)
+- next_steps: Array of concrete next actions. Name the specific task.
+- decisions: Array of decisions made this session, each with rationale
+- patterns_used: Array of techniques or approaches applied, each with context
+- preferences_expressed: Array of user preferences revealed through direction or correction
+- problems_solved: Array of problems encountered with root cause and fix
+</fields>
+
+Include a field only when the transcript contains clear evidence. Omit empty arrays. Every value must be a complete sentence.
+
+<example>
+<input>
+<previous_state>Focus: Building authentication system</previous_state>
+<transcript>
+User Asked: Let's use JWT instead of sessions for auth
+Assistant Response: Switched from express-session to jsonwebtoken. JWTs are stateless so we don't need Redis for session storage anymore. Updated the middleware to verify tokens on each request.
+User Asked: Make sure the tokens expire after 24 hours
+Assistant Response: Set expiresIn to 24h in the sign options. Also added a refresh token flow so users don't get logged out mid-work.
+</transcript>
+</input>
+<output>
+{"summary":"Implemented JWT-based authentication replacing session-based auth, with 24-hour token expiry and refresh token flow","current_focus":"Authentication system implementation","next_steps":["Test the refresh token flow with expired tokens","Add token revocation for logout"],"decisions":["Chose JWT over sessions — eliminates Redis dependency since tokens are stateless","Set 24-hour token expiry with refresh flow — balances security with user convenience"],"preferences_expressed":["User directed specific token expiry of 24 hours"]}
+</output>
+</example>
+
+<example>
+<input>
+<previous_state>Focus: Investigating test failures</previous_state>
+<transcript>
+User Asked: The CI is failing on the webhook tests
+Assistant Response: Found the issue — the test was using a hardcoded timestamp that expired. Changed it to use a relative timestamp. Also found that the webhook handler had a race condition where two events could arrive simultaneously and both pass the idempotency check. Added a mutex lock.
+User Asked: Good catch on the race condition
+</transcript>
+</input>
+<output>
+{"summary":"Fixed CI test failure caused by hardcoded timestamp and discovered a race condition in the webhook handler","current_focus":"Webhook test failures and handler reliability","problems_solved":["Fixed expired hardcoded timestamp in webhook tests — replaced with relative timestamp calculation","Fixed race condition in webhook handler where simultaneous events bypassed idempotency check — added mutex lock"],"next_steps":["Verify CI passes with the timestamp and mutex fixes"]}
+</output>
+</example>
+
+Output valid JSON only.`;
 }
 
 /**
@@ -610,7 +611,8 @@ export async function summarize(
   const apiKey = config.apiKey;
   const mode: SummarizeMode = options?.mode || "insights";
   const userName = options?.userName;
-  const systemPrompt = options?.systemPrompt || getPromptForMode(mode, userName);
+  const systemPrompt =
+    options?.systemPrompt || getPromptForMode(mode, userName);
 
   // Validate config
   if (!provider) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@voidwire/llm-summarize",
-  "version": "3.5.0",
+  "version": "3.7.0",
   "description": "Structured session insight extraction for knowledge systems",
   "type": "module",
   "main": "./index.ts",