commit-agent-cli 0.1.3 → 0.1.4

package/dist/index.js

@@ -104,11 +104,41 @@ import { intro, outro, text, spinner, confirm, isCancel, cancel, note } from "@c
 
 // src/git.ts
 import { execa } from "execa";
-async function getStagedDiff() {
-  const { stdout } = await execa("git", ["diff", "--cached"], {
+async function getStagedDiffSmart() {
+  const { stdout: fileList } = await execa("git", ["diff", "--cached", "--name-status"], {
     reject: false
   });
-  return stdout;
+  if (!fileList) return "";
+  const { stdout: stats } = await execa("git", ["diff", "--cached", "--stat"], {
+    reject: false
+  });
+  const { stdout: diff } = await execa("git", ["diff", "--cached", "--unified=1", "--no-color", "--no-prefix"], {
+    reject: false
+  });
+  const estimatedTokens = diff.length / 4;
+  if (estimatedTokens > 2e3) {
+    const { stdout: compactDiff } = await execa("git", ["diff", "--cached", "--unified=0", "--no-color", "--no-prefix"], {
+      reject: false
+    });
+    return `FILES CHANGED (${fileList.split("\n").length} files):
+${fileList}
+
+STATS:
+${stats}
+
+DIFF (function signatures only - large changeset):
+${compactDiff}
+
+Note: This is a large changeset. The diff shows only changed lines without context.`;
+  }
+  return `FILES CHANGED:
+${fileList}
+
+STATS:
+${stats}
+
+DIFF:
+${diff}`;
 }
 async function commit(message) {
   await execa("git", ["commit", "-m", message]);
@@ -324,31 +354,33 @@ async function generateCommitMessage(diff, preferences) {
   const styleGuide = preferences.commitMessageStyle === "descriptive" ? 'Be descriptive and detailed. Explain the "why" behind changes when relevant. Multi-line messages are encouraged.' : "Be concise and to the point. Keep it short, ideally one line.";
   const systemPrompt = `You are an expert developer. Your task is to generate a commit message for the provided git diff.
 
-Available Tools (use SPARINGLY - only when absolutely necessary):
-- git_commit_history: Check last 3-5 commits to understand conventions (use ONLY if diff is ambiguous)
-- git_staged_files: See list of staged files (use ONLY if you need to understand scope)
-- read_file: Read a file (ONLY if diff references unclear code - read MAX 1-2 files, prefer small files)
-- list_dir: List directory contents (RARELY needed)
+The diff provided is OPTIMIZED for token efficiency - it includes file changes, stats, and minimal context.
+
+Available Tools (use EXTREMELY RARELY):
+- git_commit_history: Check last commits (use ONLY if you truly cannot understand the convention)
+- git_staged_files: See staged files (ALREADY in the diff - don't call this)
+- read_file: Read a file (use ONLY if critical context is missing - VERY rare)
+- list_dir: List directory (almost NEVER needed)
 
-EFFICIENCY RULES - CRITICAL:
-1. The diff contains ALL the information you need in 90% of cases. START by analyzing it thoroughly.
-2. DO NOT automatically call tools. Only use them if the diff is genuinely unclear.
-3. If using read_file, read ONLY the specific function/class mentioned, not entire files.
-4. NEVER read more than 2 files total.
-5. If checking commit history, limit to 3-5 recent commits maximum.
-6. DO NOT use list_dir unless absolutely critical to understand project structure.
+CRITICAL EFFICIENCY RULES:
+1. The diff is ALREADY optimized and contains everything you need in 95%+ of cases
+2. DO NOT call ANY tools unless absolutely critical for understanding
+3. The diff shows: file list, stats, and changes - this is sufficient
+4. NEVER read files just to "understand better" - the diff IS the understanding
+5. NEVER check commit history unless the changes are completely ambiguous
+6. Aim for ZERO tool calls - generate the message directly from the diff
 
 Commit Message Rules:
 1. ${conventionalGuide}
 2. ${styleGuide}
-3. Focus on WHAT changed and WHY (if clear from diff).
-4. OUTPUT FORMAT: Your response must be ONLY the commit message. No explanations, no "Here is...", no analysis.
-5. Do NOT use markdown code blocks or formatting.
-6. If multi-line, use proper git commit format (subject line, blank line, body).
+3. Focus on WHAT changed (clear from diff) and WHY if obvious from context
+4. OUTPUT FORMAT: Your response must be ONLY the commit message. No explanations.
+5. Do NOT use markdown code blocks or formatting
+6. If multi-line, use proper git commit format (subject line, blank line, body)
 
-CRITICAL: Your ENTIRE response should be the commit message itself, nothing else. No preamble, no explanation.
+CRITICAL: Your ENTIRE response should be the commit message itself, nothing else.
 
-REMEMBER: The diff is your primary source. Tools are for edge cases only.
+DEFAULT ACTION: Read the diff, generate the message, done. NO TOOLS.
 `;
   const messages = [
     new SystemMessage(systemPrompt),
@@ -509,7 +541,7 @@ async function main() {
   }
   const s = spinner();
   s.start("Analyzing staged changes...");
-  const diff = await getStagedDiff();
+  const diff = await getStagedDiffSmart();
   if (!diff) {
     s.stop("No staged changes found.");
     cancel('Please stage your changes using "git add" first.');

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "commit-agent-cli",
-    "version": "0.1.3",
+    "version": "0.1.4",
     "description": "AI-powered git commit CLI using LangGraph and Claude 4.5",
     "main": "dist/index.js",
     "types": "./dist/index.d.ts",