claude-commit 0.3.0__tar.gz → 0.3.2__tar.gz

{claude_commit-0.3.0/src/claude_commit.egg-info → claude_commit-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-commit
-Version: 0.3.0
+Version: 0.3.2
 Summary: AI-powered git commit message generator using Claude Agent SDK
 Author-email: Johannlai <johannli666@gmail.com>
 License: MIT
@@ -97,7 +97,7 @@ For custom Claude API endpoints or proxies, set these environment variables:
 
 ```bash
 # Required: Set custom endpoint and credentials
-export ANTHROPIC_BASE_URL="https://your-endpoint.com/api/v1"
+export ANTHROPIC_BASE_URL="https://your-endpoint.com"
 export ANTHROPIC_AUTH_TOKEN="your-auth-token"
 
 # Optional: Specify custom model name

{claude_commit-0.3.0 → claude_commit-0.3.2}/README.md

@@ -68,7 +68,7 @@ For custom Claude API endpoints or proxies, set these environment variables:
 
 ```bash
 # Required: Set custom endpoint and credentials
-export ANTHROPIC_BASE_URL="https://your-endpoint.com/api/v1"
+export ANTHROPIC_BASE_URL="https://your-endpoint.com"
 export ANTHROPIC_AUTH_TOKEN="your-auth-token"
 
 # Optional: Specify custom model name

{claude_commit-0.3.0 → claude_commit-0.3.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "claude-commit"
-version = "0.3.0"
+version = "0.3.2"
 description = "AI-powered git commit message generator using Claude Agent SDK"
 readme = "README.md"
 requires-python = ">=3.9"

{claude_commit-0.3.0 → claude_commit-0.3.2}/src/claude_commit/main.py

@@ -36,9 +36,12 @@ console = Console()
 
 SYSTEM_PROMPT = """You are an expert software engineer tasked with analyzing code changes and writing excellent git commit messages.
 
-Your goal: Generate a clear, accurate, and meaningful commit message that captures the essence of the changes.
+<goal>
+Generate a clear, accurate, and meaningful commit message that captures the essence of the changes.
+</goal>
 
-Available tools you can use:
+<available_tools>
+You have access to these tools for analyzing the codebase:
 
 1. **Bash**: Run git commands and shell commands
    - `git log`, `git status`, `git diff`, `git show`
@@ -76,17 +79,27 @@ Available tools you can use:
    - Can search for specific code patterns: `{"file_path": "file.py", "old_string": "pattern to find"}`
    - Useful when you need to understand multi-line changes or context around changes
 
-Analysis approach (you decide what's necessary):
-1. IMPORTANT: First check recent commit history (git log -10 --oneline or git log -10 --pretty=format:"%s") to understand the existing commit message style
+**Pro tip**: Grep is faster than reading entire files. Use it to quickly assess impact before deciding which files to read in detail.
+</available_tools>
+
+<analysis_approach>
+Follow this approach (you decide what's necessary based on the changes):
+
+1. **IMPORTANT**: First check recent commit history to understand the existing commit message style
+   - Run: `git log -10 --oneline` or `git log -10 --pretty=format:"%s"`
    - Check if the project uses gitmoji (emojis like 🎉, ✨, 🐛, etc.)
    - Check if messages are in Chinese, English, or other languages
    - Check if they use conventional commits (feat:, fix:, etc.) or other formats
    - Note any specific patterns or conventions used
-2. Examine what files changed (git status, git diff)
+
+2. Examine what files changed
+   - Run: `git status` and `git diff` (or `git diff --cached` for staged changes)
+   
 3. For significant changes, READ the modified files to understand:
    - The purpose and context of changed functions/classes
    - How the changes fit into the larger codebase
    - The intent behind the modifications
+
 4. **USE GREP extensively** to understand code relationships (examples):
    - Modified function `process_data()`? → `grep -n "process_data("` to see where it's called
    - New class `UserManager`? → `grep -n "class.*Manager"` to find similar patterns
@@ -94,28 +107,28 @@ Analysis approach (you decide what's necessary):
    - Refactoring? → `grep --output_mode count "old_pattern"` to understand scope
    - Want context? → `grep -C 5 "function_name"` to see surrounding code
    - Find test files? → `grep -n "test_function_name"` or use glob `**/test_*.py`
-5. Consider the scope: is this a feature, fix, refactor, docs, chore, etc.?
 
-**Pro tip**: Grep is faster than reading entire files. Use it to quickly assess impact before deciding which files to read in detail.
+5. Consider the scope: is this a feature, fix, refactor, docs, chore, etc.?
+</analysis_approach>
 
-Commit message guidelines:
+<commit_message_guidelines>
+**Format Requirements**:
 - **MUST FOLLOW THE EXISTING FORMAT**: Match the style, language, and conventions used in recent commits
-- If no clear pattern exists in history, use conventional commits format (feat:, fix:, docs:, refactor:, test:, chore:, style:, perf:)
-    - feat: for new features
-    - fix: for bug fixes
-    - docs: for documentation changes
-    - refactor: for code refactoring
-    - test: for test changes
-    - chore: for chore changes
-    - style: for style changes
-    - perf: for performance improvements
-    - build: for build changes
-    - ci: for CI/CD changes
-    - revert: for reverting changes
-    - feat!: for breaking changes
-    - fix!: for breaking bug fixes
-    - perf!: for breaking performance improvements
-    - chore!: for breaking chore changes
+- If no clear pattern exists in history, use conventional commits format:
+  * feat: for new features
+  * fix: for bug fixes
+  * docs: for documentation changes, add .md to the end of the file name
+  * refactor: for code refactoring
+  * test: for test changes
+  * chore: for chore changes
+  * style: for style changes
+  * perf: for performance improvements
+  * build: for build changes
+  * ci: for CI/CD changes
+  * revert: for reverting changes
+  * feat!, fix!, perf!, chore!: for breaking changes
+
+**Structure Requirements**:
 - First line: < 50 chars (or follow existing convention), imperative mood, summarize the main change
 - **IMPORTANT**: Use multi-line format with bullet points for detailed changes:
   ```
@@ -125,29 +138,23 @@ Commit message guidelines:
   - Second change detail
   - Third change detail
   ```
+
+**Content Requirements**:
 - Be specific and meaningful (avoid vague terms like "update", "change", "modify")
 - Focus on WHAT changed and WHY (the intent), not HOW (implementation details)
 - Base your message on deep understanding, not just diff surface analysis
+</commit_message_guidelines>
 
-Examples of excellent commit messages (multi-line format):
-
-Conventional commits style(Remember to follow the existing format):
+<examples>
+**Conventional commits style** (Remember to follow the existing format):
 ```
-# for new features
 feat: add user authentication system
 
 - Implement JWT-based authentication with refresh tokens
 - Add login and registration endpoints
 - Create user session management
 - Add password hashing with bcrypt
-
-# for bug fixes
-fix: correct formatting issue
-
-- Preserve empty lines in commit messages
-
-# for document changes
-docs: update README.md
+```
 
 ```
 fix: prevent memory leak in connection pool
@@ -157,7 +164,13 @@ fix: prevent memory leak in connection pool
 - Improve error handling for failed connections
 ```
 
-With gitmoji,(✨, 🐛, ♻️, etc. ✨ for feature, 🐛 for bug, ♻️ for refactor)
+```
+fix: correct formatting issue
+
+- Preserve empty lines in commit messages
+```
+
+**With gitmoji** (✨ for feature, 🐛 for bug, ♻️ for refactor):
 ```
 ✨ add user authentication system
 
@@ -166,7 +179,7 @@ With gitmoji,(✨, 🐛, ♻️, etc. ✨ for feature, 🐛 for bug, ♻️ for
 - Create user session management
 ```
 
-In Chinese:
+**In Chinese**:
 ```
 新增：用户认证系统
 
@@ -174,13 +187,16 @@ In Chinese:
 - 添加登录和注册接口
 - 创建用户会话管理
 ```
+</examples>
 
-At the end of your analysis, output your final commit message in this format:
+<output_format>
+At the end of your analysis, output your final commit message in this exact format:
 
 COMMIT_MESSAGE:
 <your commit message here>
 
 Everything between COMMIT_MESSAGE: and the end will be used as the commit message.
+</output_format>
 """
 
 
@@ -188,7 +204,7 @@ async def generate_commit_message(
     repo_path: Optional[Path] = None,
     staged_only: bool = True,
     verbose: bool = False,
-    max_diff_lines: int = 500,
+    max_diff_lines: int = 5000,
 ) -> Optional[str]:
     """
     Generate a commit message based on current git changes.
@@ -213,51 +229,65 @@ async def generate_commit_message(
     # Build the analysis prompt - give AI freedom to explore
     prompt = f"""Analyze the git repository changes and generate an excellent commit message.
 
-Context:
+<context>
 - Working directory: {repo_path.absolute()}
 - Analysis scope: {"staged changes only (git diff --cached)" if staged_only else "all uncommitted changes (git diff)"}
-- You have access to: Bash, Read, Grep, Glob, and Edit tools
-
-Your task:
-1. **FIRST**: Check the recent commit history (e.g., `git log -3 --oneline` or `git log -3 --pretty=format:"%s"`) to understand the commit message format/style used in this project
-   - Does it use gitmoji? (emojis like ✨, 🐛, ♻️, etc.)
-   - What language? (Chinese, English, etc.)
-   - What format? (conventional commits, custom format, etc.)
-   - **IMPORTANT**: You MUST follow the same style/format/language as the existing commits
-2. Investigate the changes thoroughly. Use whatever tools and commands you need.
-3. Understand the INTENT and IMPACT of the changes, not just the surface-level diff.
-4. Read relevant files to understand context and purpose.
-5. Generate a commit message in **MULTI-LINE FORMAT** with:
-   - First line: brief summary (< 50 chars)
-   - Empty line
-   - Bullet points (starting with "-") for detailed changes
-   Example:
+- Max diff lines to analyze: {max_diff_lines} (if diff is larger, use targeted strategies)
+- Available tools: Bash, Read, Grep, Glob, and Edit
+</context>
+
+<task>
+Follow these steps to generate an excellent commit message:
+
+1. **Check commit history style** (choose ONE approach):
+   - Run `git log -3 --oneline` to see recent commits
+   - This shows you: gitmoji usage, language (Chinese/English), format (conventional commits, etc.)
+   - **MUST follow the same style/format/language as existing commits**
+
+2. **Analyze the changes**:
+   - Run `git status` to see which files changed
+   - Run `git diff --stat` first to get an overview (shows file names and line counts)
+   - Only run full `git diff` if you need to see detailed changes
+   - **IMPORTANT**: If diff is large (>{max_diff_lines} lines), use targeted strategies below instead
+
+3. **Understand the context** (use efficiently):
+   - For significant changes, READ modified files to understand their purpose
+   - Use GREP to understand code relationships WITHOUT reading entire files
+   - Use GLOB to find related files if needed
+
+4. **Generate the commit message** in MULTI-LINE FORMAT:
    ```
-   fix: correct formatting issue
+   type: brief summary (< 50 chars)
    
-   - Preserve empty lines in commit messages
-   - Update prompt to require multi-line format
-   - Add examples showing proper structure
+   - First change detail
+   - Second change detail
+   - Third change detail
    ```
-
-Recommendations (not requirements - use your judgment):
-- Start with `git log -3 --oneline` to check the commit message style
-- Then use `git status` and `git diff {"--cached" if staged_only else ""}` to see what changed
-- For non-trivial changes, READ the modified files to understand their purpose
-- **USE GREP extensively** to understand impact and context:
-  * If a function was modified, grep for its usage: `grep -n "function_name("` 
-  * If a class was added/changed, find related classes: `grep -n "class.*Base"` or similar patterns
-  * If imports changed, see where they're used: `grep -n "imported_module"`
-  * To understand scope, count usages: `grep --output_mode count "pattern"`
-  * Get context around matches: `grep -C 3 "pattern"` (3 lines before/after)
-- Consider the broader context of the codebase
-
+</task>
+
+<efficient_strategies>
+**For large diffs** (>{max_diff_lines} lines):
+- Use `git diff --stat` for overview, then `git diff <specific_file>` for key files only
+- Use `grep` to search for specific patterns instead of reading full diff
+- Focus on the most impactful changes first
+
+**Use GREP extensively** to understand code relationships:
+- Modified function `process_data()`? → `grep -n "process_data("` to see where it's called
+- New class `UserManager`? → `grep -n "class.*Manager"` to find similar patterns  
+- Imports changed? → `grep -n "from new_module import"` to see usage
+- Want context? → `grep -C 3 "function_name"` to see surrounding code
+- Count usage? → `grep --output_mode count "pattern"` to understand scope
+</efficient_strategies>
+
+<output>
 When you're confident you understand the changes, output your commit message in this exact format:
 
 COMMIT_MESSAGE:
 <your commit message>
 
 Everything after "COMMIT_MESSAGE:" will be extracted as the final commit message.
+</output>
+
 Begin your analysis now.
 """
     try:

{claude_commit-0.3.0 → claude_commit-0.3.2/src/claude_commit.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-commit
-Version: 0.3.0
+Version: 0.3.2
 Summary: AI-powered git commit message generator using Claude Agent SDK
 Author-email: Johannlai <johannli666@gmail.com>
 License: MIT
@@ -97,7 +97,7 @@ For custom Claude API endpoints or proxies, set these environment variables:
 
 ```bash
 # Required: Set custom endpoint and credentials
-export ANTHROPIC_BASE_URL="https://your-endpoint.com/api/v1"
+export ANTHROPIC_BASE_URL="https://your-endpoint.com"
 export ANTHROPIC_AUTH_TOKEN="your-auth-token"
 
 # Optional: Specify custom model name