jarvis-ai-assistant 0.1.102__py3-none-any.whl → 0.1.104__py3-none-any.whl

{jarvis_ai_assistant-0.1.102.dist-info → jarvis_ai_assistant-0.1.104.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: jarvis-ai-assistant
-Version: 0.1.102
+Version: 0.1.104
 Summary: Jarvis: An AI assistant that uses tools to interact with the system
 Home-page: https://github.com/skyfireitdiy/Jarvis
 Author: skyfire
@@ -45,10 +45,20 @@ Requires-Dist: colorama>=0.4.6
 Requires-Dist: prompt_toolkit>=3.0.0
 Requires-Dist: openai>=1.20.0
 Requires-Dist: playwright>=1.41.1
-Requires-Dist: numpy>=1.24.0
+Requires-Dist: numpy>=1.17.4
+Requires-Dist: faiss-cpu>=1.8.0
+Requires-Dist: sentence-transformers>=2.2.2
 Requires-Dist: bs4>=0.0.1
+Requires-Dist: PyMuPDF>=1.21.0
+Requires-Dist: python-docx>=0.8.11
+Requires-Dist: tiktoken>=0.3.0
 Requires-Dist: tqdm>=4.65.0
+Requires-Dist: docx>=0.2.4
 Requires-Dist: yaspin>=2.5.0
+Requires-Dist: rich>=13.3.1
+Requires-Dist: pygments>=2.15.0
+Requires-Dist: fuzzywuzzy>=0.18.0
+Requires-Dist: python-Levenshtein>=0.26.1
 Provides-Extra: dev
 Requires-Dist: pytest; extra == "dev"
 Requires-Dist: black; extra == "dev"
@@ -143,53 +153,118 @@ Jarvis supports configuration through environment variables that can be set in t
 
 ## 🎯 Usage
 
-### Main Assistant
+### Code Modification
 ```bash
+# Using main agent
 jarvis
+
+# Using code agent directly
+jarvis-code-agent
+```
+
+### Codebase Query
+```bash
+# Ask questions about the codebase
+jarvis-codebase ask "your question"
+```
+
+### Document Analysis (RAG)
+```bash
+# Build document index
+jarvis-rag --dir /path/to/documents --build
+
+# Ask questions about documents
+jarvis-rag --query "your question"
+```
+
+### Smart Shell
+```bash
+# Using full name
+jarvis-smart-shell "describe what you want to do"
+
+# Using shorthand
+jss "describe what you want to do"
 ```
 
-### Search Tool
+### Development Tools
 ```bash
-# Basic search
-jarvis-search "your query"
+# Manage git commits
+jarvis-git-commit
 
-# Show only URLs
-jarvis-search "your query" --url-only
+# Generate and manage ctags
+jarvis-ctags
 
-# Limit results
-jarvis-search "your query" --max 3
+# Manage AI platforms
+jarvis-platform
+```
+
+Each command supports `--help` flag for detailed usage information:
+```bash
+jarvis --help
+jarvis-code-agent --help
+jarvis-codebase --help
+jarvis-rag --help
+jarvis-smart-shell --help
+jarvis-platform --help
+jarvis-git-commit --help
+jarvis-ctags --help
 ```
 
 ## 🛠️ Tools
 
+### Built-in Tools
+
+| Tool | Description |
+|------|-------------|
+| read_code | Read code files with line numbers and range support |
+| execute_shell | Execute system commands and capture output |
+| search | Web search for development related queries |
+| ask_user | Interactive user input collection |
+| ask_codebase | Intelligent codebase querying and analysis |
+| code_review | Automated code review with multi-dimensional analysis |
+| file_operation | Basic file operations (read/exists) |
+| git_commiter | Automated git commit handling |
+
 ### Tool Locations
 - Built-in tools: `src/jarvis/tools/`
 - User tools: `~/.jarvis/tools/`
 
-
 ### Key Features
 
-#### 1. Self-Extending Capabilities
-- Tool generation through natural language description
-- Automatic code generation and integration
-- Dynamic capability expansion through sub-agents
-- Automatic code modification with version control
-
-#### 2. Methodology Learning
-- Automatic experience accumulation from interactions
-- Pattern recognition and methodology extraction
-- Continuous refinement through usage
-- Code modification history tracking
-
-#### 3. Adaptive Problem Solving
-- Context-aware sub-agent creation
-- Dynamic tool composition
-- Learning from execution feedback
-- Multi-model collaboration for complex tasks
-
-#### 4. Code Intelligence
-- Code modification with git integration
-- Multi-model code generation
+#### 1. Code Intelligence
+- Smart file selection and analysis based on requirements
+- Semantic codebase search and querying
+- Efficient handling of large files with context-aware reading
+- Precise patch-based code modifications
+- Automated git commit management
+
+#### 2. Multi-Model Architecture
+- Support for multiple AI platforms (Kimi/OpenAI/AI8/OYI/Ollama)
+- Platform-specific optimizations for different tasks
+- Specialized models for code generation, thinking, and general tasks
+- Streaming response support for better interaction
+- Automatic model fallback and retry mechanisms
+
+#### 3. RAG Capabilities
+- Document indexing and semantic search
+- Smart context management for large documents
+- Automatic file change detection
+- Efficient caching mechanisms
+- Multi-format document support
+
+#### 4. Development Tools
+- Interactive shell command generation
+- Code review with multi-dimensional analysis
+- Codebase-aware problem solving
+- File operations with safety checks
+- Progress tracking and error handling
+
+#### 5. User Experience
+- Beautiful console output with color support
+- Interactive multi-line input
+- Progress indicators for long operations
+- Clear error messages and handling
+- Context-aware response formatting
 
 ## 🎯 Extending Jarvis
 

jarvis_ai_assistant-0.1.104.dist-info/RECORD

@@ -0,0 +1,50 @@
+jarvis/__init__.py,sha256=16lJ0KXB1-quQt7lnzbfKIeCnmBrimAGb3_CCqEl5Co,51
+jarvis/agent.py,sha256=6r5_pv3sumUrUCd2ntWVGg7yp1KTA3JCzz2IKH582k0,20010
+jarvis/utils.py,sha256=x4wHSwoZ8pz32RJkxpZ0XdwEjikX5idXnCXUdtO8PtE,20783
+jarvis/jarvis_code_agent/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+jarvis/jarvis_code_agent/code_agent.py,sha256=8dIiFPZiWOEyIBDWUrqAdtn9g7eFrvvcCGPx5S56Ngc,6757
+jarvis/jarvis_code_agent/file_select.py,sha256=KNxalhepCM2e-V__ca8ErmbXSXHP_1xmd0UEVWUXic8,8083
+jarvis/jarvis_code_agent/patch.py,sha256=7nv-5-cPgSXZ6xfb_tmuITbCWEMRF8rLIMlQkDd7odw,4147
+jarvis/jarvis_code_agent/relevant_files.py,sha256=mlJuj65TZ9atgTi85W3BW_0GcFNDNyf6JHe9yugHIr4,3965
+jarvis/jarvis_codebase/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+jarvis/jarvis_codebase/main.py,sha256=XjqIdo_vVuVoPT8HcyuuymXk4lX5mzxOk0teRZ7Mhic,36403
+jarvis/jarvis_platform/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+jarvis/jarvis_platform/main.py,sha256=LxpOKy7wGaBxgeR5bCG5m_CoYTHVQ9Vd23J-6SE2oUU,4976
+jarvis/jarvis_rag/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+jarvis/jarvis_rag/main.py,sha256=00XeKbI6Qkd4NKRvtRLxClbCDrTJYot1bwIxWcui58k,33201
+jarvis/jarvis_smart_shell/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+jarvis/jarvis_smart_shell/main.py,sha256=yWsD9Td81sr8I1pkimlDxucDPaLWb95NuCo4LCGnT7M,3947
+jarvis/models/__init__.py,sha256=mrOt67nselz_H1gX9wdAO4y2DY5WPXzABqJbr5Des8k,63
+jarvis/models/ai8.py,sha256=QwpcdvOAixFC4BOI2AsWC9290WqcrLj6lQOiT0A3Id4,11994
+jarvis/models/base.py,sha256=nQ-rsJL1Z-gMev3TPoY7tYdwxhCJY8LG6_gtJ-maiW0,2181
+jarvis/models/kimi.py,sha256=2x60DVjX0ph2fJjKj_NICeb0q4qVBihuc_laCpH94eo,15759
+jarvis/models/ollama.py,sha256=WiUYkstaqFjiawXfuJs2GQUa3l3Y2ZWqhnKDBcF7rUQ,5672
+jarvis/models/openai.py,sha256=SAbVIvFO4q6bRl8zlDaH5bKbrP0T_zd1WzlbkPCvkwg,4121
+jarvis/models/oyi.py,sha256=nNBe-A0cOZ6vuGrnrUjeuC3N3oYRQeFazTUpFrAmx2w,15080
+jarvis/models/registry.py,sha256=nDYyGzT2uGSxbEbqp1JhuXa7bXeiMaX4hPAFAg74eyA,8683
+jarvis/tools/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+jarvis/tools/ask_codebase.py,sha256=1mLe9CHDU-NFJHmu3mxrWuA4IiHqQyum2ga31P3hLzU,2991
+jarvis/tools/ask_user.py,sha256=k0PcMqvCkf_W9kMWnFsgcFefVf1A5DhpM6WVXFMdhdQ,1823
+jarvis/tools/base.py,sha256=c0DMoDDPxmsqUYJR989zgUs7nIYRY6GWBrAdusIZKjc,656
+jarvis/tools/chdir.py,sha256=A53BNXFB9tvwoV_cxW_LpF_DfxANgAEJ8rjikTaTa-I,1813
+jarvis/tools/code_review.py,sha256=IN9eM_Zh-k7dprvnScrUz4jTqcdkkszMeXa6qIItE3w,7140
+jarvis/tools/create_code_test_agent.py,sha256=SqdIpymoDUX7L6hh5vqnZLyeVwW-QmLfytU-xkG7Gag,3462
+jarvis/tools/create_ctags_agent.py,sha256=VAZUcst9DPCO6b_VP72geBZljWjfied09EPgSokYA0E,4878
+jarvis/tools/create_sub_agent.py,sha256=0lZDtYRFjr9C9xtBKV-sxWfhK0TX-cxAHj3Zez76A4s,2853
+jarvis/tools/execute_shell.py,sha256=bawfof8bUg3f9bjyCSifLa9bU-hkNoNOuos22uZffdg,2564
+jarvis/tools/file_operation.py,sha256=-1U_J5SEuBjRylzEl7wvCfjspNv6aA49UvFHLNQ3bJU,4098
+jarvis/tools/find_in_codebase.py,sha256=bxILvDox2oGd0XZ-gvfWjH7Yj4ciyMYC3VJI3aWiMw8,2455
+jarvis/tools/git_commiter.py,sha256=7kJhtTyu09Cp4VP_IDKRrKXIKxQXkBF1drCgPkYzk6M,2549
+jarvis/tools/methodology.py,sha256=yZldtjPZpNq8eGJ6IbhwHB0v3cFUtfPd14r7LDCo5IU,5622
+jarvis/tools/rag.py,sha256=2fQHqc4bw8JM-OxGTsHobLIOTo8Mip3rdtJCmAoY8XU,4952
+jarvis/tools/read_code.py,sha256=5DGmeXTgumAiG0RP1xB4sF4NdmBm5BEGjRRlIBzjGnQ,4002
+jarvis/tools/read_webpage.py,sha256=JCReSXhkDHDkQ606sZYIKG1Itlprjpmu1sSbF-Ed-jI,2478
+jarvis/tools/registry.py,sha256=81Q_x9BJV6SIfPWURq4uzXxP2JCiFeaGbGM1IO5FSy4,11658
+jarvis/tools/search.py,sha256=IciWpdKoa03Kl5J1SdblI2VhkUBoIRuLHHM2X4KlMWE,9209
+jarvis/tools/select_code_files.py,sha256=bjJGwCNw0Ue_8jW60K1gcy1rUgKqoHihicu5SS58WNk,1890
+jarvis_ai_assistant-0.1.104.dist-info/LICENSE,sha256=AGgVgQmTqFvaztRtCAXsAMryUymB18gZif7_l2e1XOg,1063
+jarvis_ai_assistant-0.1.104.dist-info/METADATA,sha256=_AFsS0M4n0yuT_7xZfUpB8UtgS0gYm-wfcGLxgnTRDY,13594
+jarvis_ai_assistant-0.1.104.dist-info/WHEEL,sha256=In9FTNxeP60KnTkGw7wk6mJPYd_dQSjEZmXdBdMCI-8,91
+jarvis_ai_assistant-0.1.104.dist-info/entry_points.txt,sha256=9wmOanjcRugTjJWeDg4lKiUtePaymFUOIi-8Gm2azCU,502
+jarvis_ai_assistant-0.1.104.dist-info/top_level.txt,sha256=1BOxyWfzOP_ZXj8rVTDnNCJ92bBGB0rwq8N1PCpoMIs,7
+jarvis_ai_assistant-0.1.104.dist-info/RECORD,,

jarvis_ai_assistant-0.1.104.dist-info/entry_points.txt

@@ -0,0 +1,11 @@
+[console_scripts]
+jarvis = jarvis.agent:main
+jarvis-code-agent = jarvis.jarvis_code_agent.code_agent:main
+jarvis-code-review = jarvis.tools.code_review:main
+jarvis-codebase = jarvis.jarvis_codebase.main:main
+jarvis-ctags = jarvis.tools.create_ctags_agent:main
+jarvis-git-commit = jarvis.tools.git_commiter:main
+jarvis-platform = jarvis.jarvis_platform.main:main
+jarvis-rag = jarvis.jarvis_rag.main:main
+jarvis-smart-shell = jarvis.jarvis_smart_shell.main:main
+jss = jarvis.jarvis_smart_shell.main:main

jarvis/jarvis_code_agent/main.py

@@ -1,200 +0,0 @@
-from jarvis.agent import Agent
-from jarvis.tools.registry import ToolRegistry
-from jarvis.utils import OutputType, PrettyOutput, get_multiline_input, init_env
-
-
-
-
-system_prompt = """You are Jarvis Code Agent, an AI code development assistant specialized in code analysis, modification, and version control. Your role is to help users with coding tasks systematically and reliably.
-
-DEVELOPMENT WORKFLOW:
-1. Task Analysis
-   - Understand the requirements thoroughly
-   - IMPORTANT: Before suggesting any changes:
-     * Thoroughly examine existing code implementation
-     * Never assume code structure or implementation details
-     * Always verify current code behavior and patterns
-   - Break down complex tasks into subtasks
-   - IMPORTANT: Each subtask should:
-     * Modify only ONE file
-     * Change no more than 20 lines of code
-     * Be focused and atomic
-   - Define success criteria
-
-2. Code Discovery & Analysis
-   - Initial code search:
-     * CRITICAL: Always examine actual code implementation first
-     * Use shell commands to find and understand patterns:
-       <TOOL_CALL>
-       name: execute_shell
-       arguments:
-           command: grep -r 'pattern' directory/
-       </TOOL_CALL>
-       <TOOL_CALL>
-       name: execute_shell
-       arguments:
-           command: grep -A 5 -B 5 'pattern' file.py
-       </TOOL_CALL>
-     * Use shell commands to locate files:
-       <TOOL_CALL>
-       name: execute_shell
-       arguments:
-           command: find . -name 'pattern'
-       </TOOL_CALL>
-     * Use shell commands to preview:
-       <TOOL_CALL>
-       name: execute_shell
-       arguments:
-           command: head -n 50 file.py
-       </TOOL_CALL>
-   - File selection and confirmation:
-     * Let user confirm selection:
-       <TOOL_CALL>
-       name: select_code_files
-       arguments:
-           related_files:
-               - auth.py
-               - user.py
-           root_dir: .
-       </TOOL_CALL>
-
-3. Modification Planning
-   - CRITICAL: Base all plans on actual code implementation, not assumptions
-   - Generate a detailed modification plan based on:
-     * Current code structure and patterns
-     * Existing implementation details
-     * User requirements
-     * Actual code conditions
-
-4. Code Implementation
-   - For small changes (≤20 lines):
-     <TOOL_CALL>
-     name: execute_code_modification
-     arguments:
-         task: Add password validation
-         structured_plan:
-             auth.py: Add password strength check in validate_password()
-     </TOOL_CALL>
-   - For large changes:
-     <TOOL_CALL>
-     name: create_code_sub_agent
-     arguments:
-         name: code_sub_agent
-         subtask: Implement new authentication flow
-     </TOOL_CALL>
-
-FILE SELECTION WORKFLOW:
-1. Initial Search
-   - Use shell commands to find relevant files
-   - Review search results for relevance
-
-2. User Confirmation
-   - Use select_code_files to:
-     * Display found files
-     * Let user review selection
-     * Allow file list adjustment
-     * Enable file supplementation
-
-3. File Validation
-   - Verify selected files exist
-   - Check file permissions
-   - Validate file types
-   - Ensure completeness
-
-CODE SEARCH BEST PRACTICES:
-- Use grep for pattern matching:
-  * grep -r "pattern" directory/
-  * grep -A 5 -B 5 for context
-  * grep -n for line numbers
-- Use find for file location:
-  * find . -name "pattern"
-  * find . -type f -exec grep "pattern" {} \\;
-- Use head/tail for previews:
-  * head -n 50 file.py
-  * tail -n 50 file.py
-  * head -n +100 | tail -n 50
-- Avoid loading entire large files
-- Focus on relevant sections
-- Use line numbers for reference
-
-SUBTASK MANAGEMENT RULES:
-- One subtask = One file modification
-- Each subtask ≤20 lines of code changes
-- Break down larger changes into multiple subtasks
-- Create separate sub-agent for each subtask
-- Follow dependency order in execution
-- Verify each change independently
-
-CODE MODIFICATION LIMITS:
-- Maximum 20 lines per change
-- Count both added and modified lines
-- Exclude comment and blank lines
-- Include only actual code changes
-- Split larger changes into subtasks
-
-ITERATION GUIDELINES:
-- Each iteration should be small and focused
-- Keep changes minimal and clear
-- Verify changes before moving forward
-- Document issues and solutions
-- Learn from previous iterations
-
-TOOL USAGE:
-1. Analysis Tools:
-   - execute_shell: Run grep/find/head/tail commands
-   - find_files: Search and identify relevant code files in the codebase based on requirements or problems
-   - select_code_files: Confirm and supplement files
-   - ask_user: Ask user for confirmation and information if needed
-   - create_code_sub_agent: Create agent for each small change
-   - file_operation: Read files
-   - search: Use Bing search engine to search for information, and extract key information based on the question
-   - thinker: Deep thinking and logical reasoning
-2. Planning Tools:
-   - thinker: Generate a detailed modification plan based on user requirements and actual code conditions.
-   - create_code_sub_agent: Create agent for each small change
-   - ask_user: Ask user for confirmation and information if needed
-
-3. Implementation Tools:
-   - execute_shell: Run shell commands, some changes can use sed/awk/etc. to modify the code
-   - execute_code_modification: Apply small changes (≤20 lines)
-   - file_operation: Read, write, or append to files
-
-IMPORTANT:
-1. If you can start executing the task, please start directly without asking the user if you can begin.
-2. NEVER assume code structure or implementation - always examine the actual code first.
-3. Base all suggestions and modifications on the current implementation, not assumptions.
-4. If code implementation is unclear, use available tools to investigate before proceeding.
-5. Before you start modifying the code, you should ask the user for confirmation of the modification plan.
-6. For some small changes, you can modify the code using the execute_shell tool directly or use file_operation tool to read the file and modify it.
-"""
-
-def main():
-    """Jarvis main entry point"""
-    # Add argument parser
-    init_env()
-
-
-    try:
-        tool_registry = ToolRegistry()
-        tool_registry.dont_use_tools(["create_sub_agent"])
-        # Get global model instance
-        agent = Agent(system_prompt=system_prompt, name="Jarvis Code Agent", tool_registry=tool_registry)
-
-        # Interactive mode
-        while True:
-            try:
-                user_input = get_multiline_input("Please enter your task (input empty line to exit):")
-                if not user_input or user_input == "__interrupt__":
-                    break
-                agent.run(user_input)
-            except Exception as e:
-                PrettyOutput.print(f"Error: {str(e)}", OutputType.ERROR)
-
-    except Exception as e:
-        PrettyOutput.print(f"Initialization error: {str(e)}", OutputType.ERROR)
-        return 1
-
-    return 0
-
-if __name__ == "__main__":
-    exit(main())

jarvis/jarvis_coder/git_utils.py

@@ -1,123 +0,0 @@
-import os
-from typing import List
-import yaml
-import time
-from jarvis.utils import OutputType, PrettyOutput, find_git_root, while_success
-from jarvis.models.registry import PlatformRegistry
-
-def has_uncommitted_files() -> bool:
-    """Check if there are uncommitted files in the repository"""
-    # Get unstaged modifications
-    unstaged = os.popen("git diff --name-only").read()
-    # Get staged but uncommitted modifications
-    staged = os.popen("git diff --cached --name-only").read()
-    # Get untracked files
-    untracked = os.popen("git ls-files --others --exclude-standard").read()
-    
-    return bool(unstaged or staged or untracked)
-
-def generate_commit_message(git_diff: str) -> str:
-    """Generate commit message based on git diff and feature description"""
-    prompt = f"""You are an experienced programmer, please generate a concise and clear commit message based on the following code changes and feature description:
-
-Code changes:
-Git Diff:
-{git_diff}
-
-Please follow these rules:
-1. Write in English
-2. Use conventional commit message format: <type>(<scope>): <subject>
-3. Keep it concise, no more than 50 characters
-4. Accurately describe the main content of code changes
-5. Prioritize feature description and changes in git diff
-6. Only generate the commit message text, do not output anything else
-"""
-    
-    model = PlatformRegistry().get_global_platform_registry().get_normal_platform()
-    response = model.chat_until_success(prompt)
-        
-    return ';'.join(response.strip().split("\n"))
-
-def save_edit_record(record_dir: str, commit_message: str, git_diff: str) -> None:
-    """Save code modification record"""
-    # Get next sequence number
-    existing_records = [f for f in os.listdir(record_dir) if f.endswith('.yaml')]
-    next_num = 1
-    if existing_records:
-        last_num = max(int(f[:4]) for f in existing_records)
-        next_num = last_num + 1
-    
-    # Create record file
-    record = {
-        "timestamp": time.strftime("%Y-%m-%d %H:%M:%S"),
-        "commit_message": commit_message,
-        "git_diff": git_diff
-    }
-    
-    record_path = os.path.join(record_dir, f"{next_num:04d}.yaml")
-    with open(record_path, "w", encoding="utf-8") as f:
-        yaml.safe_dump(record, f, allow_unicode=True)
-    
-    PrettyOutput.print(f"Modification record saved: {record_path}", OutputType.SUCCESS) 
-
-
-def init_git_repo(root_dir: str) -> str:
-    git_dir = find_git_root(root_dir)
-    if not git_dir:
-        git_dir = root_dir
-
-    PrettyOutput.print(f"Git root directory: {git_dir}", OutputType.INFO)
-
-    # 1. Check if the code repository path exists, if it does not exist, create it
-    if not os.path.exists(git_dir):
-        PrettyOutput.print(
-            "Root directory does not exist, creating...", OutputType.INFO)
-        os.makedirs(git_dir)
-
-    os.chdir(git_dir)
-
-    # 3. Process .gitignore file
-    gitignore_path = os.path.join(git_dir, ".gitignore")
-    gitignore_modified = False
-    jarvis_ignore_pattern = ".jarvis"
-
-    # 3.1 If .gitignore does not exist, create it
-    if not os.path.exists(gitignore_path):
-        PrettyOutput.print("Create .gitignore file", OutputType.INFO)
-        with open(gitignore_path, "w", encoding="utf-8") as f:
-            f.write(f"{jarvis_ignore_pattern}\n")
-        gitignore_modified = True
-    else:
-        # 3.2 Check if it already contains the .jarvis pattern
-        with open(gitignore_path, "r", encoding="utf-8") as f:
-            content = f.read()
-        
-        # 3.2 Check if it already contains the .jarvis pattern
-        if jarvis_ignore_pattern not in content.split("\n"):
-            PrettyOutput.print("Add .jarvis to .gitignore", OutputType.INFO)
-            with open(gitignore_path, "a", encoding="utf-8") as f:
-                # Ensure the file ends with a newline
-                if not content.endswith("\n"):
-                    f.write("\n")
-                f.write(f"{jarvis_ignore_pattern}\n")
-            gitignore_modified = True
-
-    # 4. Check if the code repository is a git repository, if not, initialize the git repository
-    if not os.path.exists(os.path.join(git_dir, ".git")):
-        PrettyOutput.print("Initialize Git repository", OutputType.INFO)
-        os.system("git init")
-        os.system("git add .")
-        os.system("git commit -m 'Initial commit'")
-    # 5. If .gitignore is modified, commit the changes
-    elif gitignore_modified:
-        PrettyOutput.print("Commit .gitignore changes", OutputType.INFO)
-        os.system("git add .gitignore")
-        os.system("git commit -m 'chore: update .gitignore to exclude .jarvis-* files'")
-    # 6. Check if there are uncommitted files in the code repository, if there are, commit once
-    elif has_uncommitted_files():
-        PrettyOutput.print("Commit uncommitted changes", OutputType.INFO)
-        os.system("git add .")
-        git_diff = os.popen("git diff --cached").read()
-        commit_message = generate_commit_message(git_diff)
-        os.system(f"git commit -m '{commit_message}'")
-    return git_dir