git-copilot-commit 0.1.15__tar.gz → 0.1.16__tar.gz

{git_copilot_commit-0.1.15 → git_copilot_commit-0.1.16}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: git-copilot-commit
-Version: 0.1.15
+Version: 0.1.16
 Summary: Automatically generate and commit changes using copilot
 Author-email: Dheepak Krishnamurthy <1813121+kdheepak@users.noreply.github.com>
 License-File: LICENSE
@@ -100,7 +100,6 @@ Usage: git-copilot-commit commit [OPTIONS]
 
 Options:
   -a, --all         Stage all files before committing
-  -v, --verbose     Show verbose output
   -m, --model TEXT  Model to use for generating commit message
   -y, --yes         Automatically accept the generated commit message
   --help            Show this message and exit.
@@ -152,10 +151,10 @@ Commit all changes:
 git-copilot-commit commit --all
 ```
 
-Verbose output:
+Accept the generated commit message without editing:
 
 ```bash
-git-copilot-commit commit --verbose
+git-copilot-commit commit --yes
 ```
 
 Use a specific model:
@@ -205,8 +204,7 @@ Now you can run:
 
 ```bash
 git ai-commit
-git ai-commit --all --verbose
-git ai-commit --model claude-3.5-sonnet
+git ai-commit --all --yes --model claude-3.5-sonnet
 ```
 
 Additionally, show more context in diffs by running the following command:

{git_copilot_commit-0.1.15 → git_copilot_commit-0.1.16}/README.md

@@ -87,7 +87,6 @@ Usage: git-copilot-commit commit [OPTIONS]
 
 Options:
   -a, --all         Stage all files before committing
-  -v, --verbose     Show verbose output
   -m, --model TEXT  Model to use for generating commit message
   -y, --yes         Automatically accept the generated commit message
   --help            Show this message and exit.
@@ -139,10 +138,10 @@ Commit all changes:
 git-copilot-commit commit --all
 ```
 
-Verbose output:
+Accept the generated commit message without editing:
 
 ```bash
-git-copilot-commit commit --verbose
+git-copilot-commit commit --yes
 ```
 
 Use a specific model:
@@ -192,8 +191,7 @@ Now you can run:
 
 ```bash
 git ai-commit
-git ai-commit --all --verbose
-git ai-commit --model claude-3.5-sonnet
+git ai-commit --all --yes --model claude-3.5-sonnet
 ```
 
 Additionally, show more context in diffs by running the following command:

{git_copilot_commit-0.1.15 → git_copilot_commit-0.1.16}/src/git_copilot_commit/cli.py

@@ -41,38 +41,6 @@ def main(
         raise typer.Exit()
 
 
-def display_file_status(status: GitStatus) -> None:
-    """Display file status in a rich table."""
-    if not status.files:
-        return
-
-    table = Table(title="Git Status")
-    table.add_column("Status", style="yellow", width=8)
-    table.add_column("File", style="white")
-
-    # Group files by status
-    staged = status.staged_files
-    unstaged = status.unstaged_files
-    untracked = status.untracked_files
-
-    if staged:
-        table.add_row("[green]Staged[/green]", "", style="dim")
-        for file in staged:
-            table.add_row(f"  {file.staged_status}", file.path)
-
-    if unstaged:
-        table.add_row("[yellow]Unstaged[/yellow]", "", style="dim")
-        for file in unstaged:
-            table.add_row(f"  {file.status}", file.path)
-
-    if untracked:
-        table.add_row("[red]Untracked[/red]", "", style="dim")
-        for file in untracked:
-            table.add_row("  ?", file.path)
-
-    console.print(table)
-
-
 def generate_commit_message(
     repo: GitRepository, status: GitStatus, model: str | None = None
 ) -> str:
@@ -120,11 +88,11 @@ The guidelines for the commit messages are as follows:
 
 3. Scope (Optional but encouraged):
 
-- Enclose in parentheses, e.g., feat(auth): add login endpoint.
-- Use the affected module, component, or area: `auth`, `api`, `ui`, `database`, `config`.
-- For multiple files in same area, use the broader scope: `feat(auth): add login and logout endpoints`.
-- For single files, you may use filename: `fix(user-service): handle null email validation`.
-- Scope should be a single word or hyphenated phrase describing the affected module.
+- Enclose in parentheses
+- Use the affected module, component, or area
+- For multiple files in same area, use the broader scope
+- For single files, you may use filename
+- Scope should be a single word or hyphenated phrase describing the affected module
 
 4. Description:
 
@@ -132,7 +100,7 @@ The guidelines for the commit messages are as follows:
 - Be concise yet informative.
 - Focus on the primary change, not all details.
 - Do not make assumptions about why the change was made or how it works.
-- Do not say "improving code readability" or similar; focus on just the change itself.
+- When bumping versions, do not mention the names of the files.
 
 5. Analyzing Git Diffs:
 
@@ -141,21 +109,6 @@ The guidelines for the commit messages are as follows:
 - Identify the primary purpose of the change set.
 - If changes span multiple unrelated areas, focus on the most significant one.
 
-Examples:
-
-✅ Good Commit Messages:
-
-- feat(api): add user authentication with JWT
-- fix(database): handle connection retries properly
-- docs(readme): update installation instructions
-- refactor(utils): simplify date parsing logic
-- chore(deps): update dependencies to latest versions
-- feat(auth): implement OAuth2 integration
-- fix(payments): resolve double-charging bug in subscription renewal
-- refactor(database): extract query builder into separate module
-- chore(ci): add automated security scanning to pipeline
-- docs(api): add OpenAPI specifications for user endpoints
-
 ❌ Strongly Avoid:
 
 - Vague descriptions: "fixed bug", "updated code", "made changes"
@@ -165,12 +118,12 @@ Examples:
 - Not in imperative mood: "new feature", "updates stuff"
 
 Given a Git diff, a list of modified files, or a short description of changes,
-generate a single clear and structured Conventional Commit message following the above rules.
+generate a single, short, clear and structured Conventional Commit message following the above rules.
 If multiple changes are detected, prioritize the most important changes in a single commit message.
 Do not add any body or footer.
-You can only give one reply for each conversation turn.
+You can only give one reply for each conversation.
 
-Avoid wrapping the whole response in triple backticks or single backticks.
+Do not wrap the response in triple backticks or single backticks.
 Return the commit message as the output without any additional text, explanations, or formatting markers.
 """
     )
@@ -202,7 +155,6 @@ def commit(
     all_files: bool = typer.Option(
         False, "--all", "-a", help="Stage all files before committing"
     ),
-    verbose: bool = typer.Option(False, "--verbose", "-v", help="Show verbose output"),
     model: str | None = typer.Option(
         None, "--model", "-m", help="Model to use for generating commit message"
     ),
@@ -231,10 +183,6 @@ def commit(
         console.print("[yellow]No changes to commit.[/yellow]")
         raise typer.Exit()
 
-    # Display current status
-    if verbose:
-        display_file_status(status)
-
     # Handle staging based on options
     if all_files:
         repo.stage_files()  # Stage all files
@@ -280,12 +228,6 @@ def commit(
     # Display commit message
     console.print(Panel(commit_message, title="Commit Message", border_style="green"))
 
-    # Show what will be committed in verbose mode
-    if verbose:
-        console.print("\n[bold]Changes to be committed:[/bold]")
-        for file in status.staged_files:
-            console.print(f"  {file.staged_status} {file.path}")
-
     # Confirm commit or edit message (skip if --yes flag is used)
     if yes:
         # Automatically commit with generated message