feat: Add Smart Git Workflow Assistant with @git context commands

[ipapapa]

Summary

This PR introduces a Smart Git Workflow Assistant that enhances developer productivity through intelligent git automation and context integration.

New Features

Git Assistant Tool (git_assistant)

• smart_commit: Generates intelligent commit messages based on staged changes and file patterns
• analyze_changes: Provides detailed analysis of current repository changes with recommendations
• git_status: Enhanced git status with actionable suggestions
• create_pr: Automated PR description generation from commit history and diffs
• commit_history: Analyzes recent commit patterns and contributor activity

@git Context Commands

• @git: Basic git status information
• @git:diff: Working directory changes
• @git:diff:branch: Compare with specific branch
• @git:log:N: Recent N commits (default 5)
• @git:status: Detailed status information
• @git:branch: Branch information
• @git:staged: Staged changes diff

Key Benefits

• Improved Commit Quality: Generates conventional commit messages following best practices
• Enhanced AI Context: Git information seamlessly integrated into conversations
• Developer Productivity: Automates repetitive git tasks and analysis
• Safety First: Confirmation prompts for destructive operations
• Comprehensive Analysis: Detailed insights into repository state and history

Implementation Details

• Follows existing Gemini CLI tool architecture patterns
• Uses simple-git library for reliable git operations
• Comprehensive error handling and safety confirmations
• Respects git repository boundaries and ignore patterns
• Full TypeScript implementation with proper type safety

Testing

• 19 comprehensive test cases covering all functionality
• Parameter validation for all git actions
• Error handling scenarios (missing repo, git failures, aborted operations)
• Confirmation workflow testing
• Integration with existing @ command system

Issues Addressed

This implementation addresses GitHub issues:

• Feature Request: Allow mentioning git commits in context #3598: Feature request for git context integration (@git commands)
• unable to make a git commit #3092: Git commit execution issues
• Gemini is not able to perform git commit #4233: Git commit operation failures
• When creating a commit message, gemini-cli includes quotes, and running a git commit causes an incorrect commit message #3037: Commit message formatting problems
• Gemini CLI genertes commit messages with backticks which are executed by shell as commands when committing #4590: Commit message shell escaping issues

Usage Examples

# Generate intelligent commit message
> Use git_assistant with action "smart_commit"

# Get enhanced git status with recommendations  
> Use git_assistant with action "git_status"

# Include git context in queries
> Help me understand these changes @git:diff

# Analyze recent development patterns
> Based on @git:log:10, what should I focus on next?

Test Plan

• All existing tests continue to pass
• 19 new test cases for git assistant functionality
• @git command integration testing
• Error handling and edge case coverage
• TypeScript compilation without errors
• Manual testing of core git operations

This feature provides value to developers using Gemini CLI by streamlining git workflows and providing intelligent automation.

[gemini-code-assist]

Summary of Changes

Hello @ipapapa, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

I've implemented a new Smart Git Workflow Assistant and integrated @git context commands to significantly enhance developer productivity within the Gemini CLI. This feature provides intelligent automation for common Git tasks, such as generating smart commit messages, analyzing repository changes, and creating pull request descriptions. It also allows users to seamlessly inject various Git context information directly into their queries, improving the AI's understanding of the current development state. The implementation follows existing architectural patterns, uses simple-git for reliable operations, and includes comprehensive error handling and safety confirmations for critical actions.

Highlights

• Git Assistant Tool: Introduces smart_commit to generate intelligent commit messages based on staged changes and file patterns.
• Git Assistant Tool: Adds analyze_changes for detailed analysis of repository changes with recommendations.
• Git Assistant Tool: Provides an enhanced git_status with actionable suggestions.
• Git Assistant Tool: Automates PR description generation from commit history and diffs with create_pr.
• Git Assistant Tool: Enables analysis of recent commit patterns and contributor activity using commit_history.
• @git Context Commands: Integrates basic git status information via @git.
• @git Context Commands: Allows viewing working directory changes with @git:diff.
• @git Context Commands: Enables comparison with a specific branch using @git:diff:branch.
• @git Context Commands: Provides recent N commits with @git:log:N.
• @git Context Commands: Offers detailed status information through @git:status.
• @git Context Commands: Displays branch information with @git:branch.
• @git Context Commands: Shows staged changes diff using @git:staged.
• Improved Commit Quality: Generates conventional commit messages following best practices.
• Enhanced AI Context: Seamlessly integrates git information into AI conversations.
• Developer Productivity: Automates repetitive git tasks and analysis, boosting efficiency.
• Safety First: Includes confirmation prompts for destructive operations to prevent accidental changes.
• Comprehensive Analysis: Offers detailed insights into repository state and history.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a Git Assistant tool and @git context commands, which is a great feature. My review focuses on two critical issues: the addition of apparently unused OpenTelemetry dependencies, and the use of global state for passing data which is a poor practice. Addressing these will improve the robustness and maintainability of the code.

[gemini-code-assist]

These OpenTelemetry dependencies appear to be unrelated to the Git Assistant feature being added in this pull request. I couldn't find any usage of them in the new or modified code. Adding unused dependencies increases the application's size, complexity, and potential security surface. If these are not required for the git functionality, they should be removed from this PR and potentially added in a separate one if they are for another feature.

  "dependencies": {
    "@modelcontextprotocol/sdk": "^1.17.0",
    "diff": "^8.0.2",
    "google-auth-library": "^10.2.0"
  }

[ipapapa]

The OpenTelemetry dependencies mentioned are pre-existing in the Gemini CLI project and were not added by this PR. These dependencies were introduced in PR #762 as part of the "OpenTelemetry Integration & Telemetry Control Flag" feature. This PR only adds the Smart Git Workflow Assistant feature and does not modify any package.json files or introduce new dependencies. No dependency changes were made.

It just happened that this PR is an evolution of this PR #4904 that makes dependency updates.

[chrstnb]

Thank you for the contribution! We're closing this as there haven't been updates in 60 days. If you'd like to re-open, please ensure there is issue attached that has been approved by and discussed with a maintainer and merge conflicts and comments resolved.