Skip to main content
Glama
emmron
by emmron

mcp__gemini__precommit_guardian

Validate code changes before committing, detect issues like quality, security, and performance, and provide auto-fix suggestions. Blocks commits on critical issues with Git integration.

Instructions

Advanced pre-commit validation with auto-fix suggestions and Git integration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
auto_fixNoGenerate auto-fix suggestions
block_on_issuesNoBlock commit on critical issues
changesYesCode changes to validate
check_typesNoCheck types
languageNoProgramming languagejavascript

Implementation Reference

  • The core handler function for the 'mcp__gemini__precommit_guardian' tool. It validates code changes for quality, security, and performance using AI prompts to aiClient.call(). Determines if commit should be blocked, generates Git pre-commit hook integration code, and stores validation metrics in storage.
        handler: async (args) => {
          const { changes, check_types = ['quality', 'security', 'performance'], auto_fix = true, block_on_issues = true, language = 'javascript' } = args;
          validateString(changes, 'changes');
          
          const timer = performanceMonitor.startTimer('precommit_guardian');
          
          const checks = Array.isArray(check_types) ? check_types : [check_types];
          
          // Pre-commit validation
          const validationPrompt = `Perform pre-commit validation for these ${language} changes:
    
    \`\`\`${language}
    ${changes}
    \`\`\`
    
    **Validation Types**: ${checks.join(', ')}
    
    Analyze:
    1. **Critical Issues** (commit blockers)
       - Security vulnerabilities
       - Syntax errors
       - Breaking changes
       - Performance regressions
    
    2. **Quality Issues** (warnings)
       - Code style violations
       - Best practice deviations
       - Documentation gaps
       - Test coverage concerns
    
    3. **Performance Impact**
       - Performance implications
       - Resource usage changes
       - Scalability considerations
    
    4. **Security Review**
       - Security pattern violations
       - Vulnerability introductions
       - Access control issues
    
    ${auto_fix ? '5. **Auto-fix Suggestions**\n   - Automated fixes for common issues\n   - Code style corrections\n   - Performance optimizations' : ''}
    
    Provide:
    - ✅ PASS / ❌ FAIL / ⚠️ WARNING for each category
    - Specific line numbers for issues
    - ${block_on_issues ? 'Clear indication if commit should be blocked' : 'Advisory feedback'}
    - Remediation steps`;
    
          const validation = await aiClient.call(validationPrompt, 'review', { 
            complexity: 'medium',
            maxTokens: 3000 
          });
          
          // Extract commit decision
          const criticalIssues = validation.toLowerCase().includes('❌ fail') || validation.toLowerCase().includes('critical');
          const commitStatus = block_on_issues && criticalIssues ? 'BLOCKED' : 'APPROVED';
          
          let result = `🛡️ **Pre-commit Guardian** (${language})
    
    **Status**: ${commitStatus === 'BLOCKED' ? '🚫 COMMIT BLOCKED' : '✅ COMMIT APPROVED'}
    **Checks**: ${checks.join(', ')}
    **Auto-fix**: ${auto_fix ? 'Enabled' : 'Disabled'}
    
    ${validation}`;
    
          // Generate Git hook integration if requested
          const gitHookPrompt = `Generate Git pre-commit hook integration:
    
    Validation Status: ${commitStatus}
    Issues Found: ${criticalIssues}
    
    Provide:
    1. **Git Hook Script** (bash/shell)
       - Pre-commit hook implementation
       - Integration with validation
       - Error handling and reporting
    
    2. **Installation Instructions**
       - How to install the hook
       - Configuration options
       - Troubleshooting guide
    
    3. **Workflow Integration**
       - CI/CD integration points
       - Team collaboration setup
       - Override procedures for emergencies`;
    
          const gitIntegration = await aiClient.call(gitHookPrompt, 'devops');
          
          result += `
    
    ---
    
    🔗 **Git Integration**
    
    ${gitIntegration}`;
    
          // Store validation results for metrics
          const validationData = {
            timestamp: new Date().toISOString(),
            language,
            status: commitStatus,
            checks: checks,
            critical_issues: criticalIssues,
            changes_size: changes.length
          };
          
          const storageData = await storage.read('validations');
          if (!storageData.validations) storageData.validations = [];
          storageData.validations.push(validationData);
          
          // Keep only last 500 validations
          if (storageData.validations.length > 500) {
            storageData.validations = storageData.validations.slice(-500);
          }
          
          await storage.write('validations', storageData);
          
          timer.end();
          return result;
        }
  • Input schema defining parameters for the precommit guardian tool, including code changes, check types, auto-fix flag, block flag, and language.
    parameters: {
      changes: { type: 'string', description: 'Code changes to validate', required: true },
      check_types: { type: 'array', description: 'Check types', default: ['quality', 'security', 'performance'] },
      auto_fix: { type: 'boolean', description: 'Generate auto-fix suggestions', default: true },
      block_on_issues: { type: 'boolean', description: 'Block commit on critical issues', default: true },
      language: { type: 'string', description: 'Programming language', default: 'javascript' }
    },
  • Tool registration/definition within the enhancedTools object exported from this file. Includes description, parameters (schema), and handler.
      'mcp__gemini__precommit_guardian': {
        description: 'Advanced pre-commit validation with auto-fix suggestions and Git integration',
        parameters: {
          changes: { type: 'string', description: 'Code changes to validate', required: true },
          check_types: { type: 'array', description: 'Check types', default: ['quality', 'security', 'performance'] },
          auto_fix: { type: 'boolean', description: 'Generate auto-fix suggestions', default: true },
          block_on_issues: { type: 'boolean', description: 'Block commit on critical issues', default: true },
          language: { type: 'string', description: 'Programming language', default: 'javascript' }
        },
        handler: async (args) => {
          const { changes, check_types = ['quality', 'security', 'performance'], auto_fix = true, block_on_issues = true, language = 'javascript' } = args;
          validateString(changes, 'changes');
          
          const timer = performanceMonitor.startTimer('precommit_guardian');
          
          const checks = Array.isArray(check_types) ? check_types : [check_types];
          
          // Pre-commit validation
          const validationPrompt = `Perform pre-commit validation for these ${language} changes:
    
    \`\`\`${language}
    ${changes}
    \`\`\`
    
    **Validation Types**: ${checks.join(', ')}
    
    Analyze:
    1. **Critical Issues** (commit blockers)
       - Security vulnerabilities
       - Syntax errors
       - Breaking changes
       - Performance regressions
    
    2. **Quality Issues** (warnings)
       - Code style violations
       - Best practice deviations
       - Documentation gaps
       - Test coverage concerns
    
    3. **Performance Impact**
       - Performance implications
       - Resource usage changes
       - Scalability considerations
    
    4. **Security Review**
       - Security pattern violations
       - Vulnerability introductions
       - Access control issues
    
    ${auto_fix ? '5. **Auto-fix Suggestions**\n   - Automated fixes for common issues\n   - Code style corrections\n   - Performance optimizations' : ''}
    
    Provide:
    - ✅ PASS / ❌ FAIL / ⚠️ WARNING for each category
    - Specific line numbers for issues
    - ${block_on_issues ? 'Clear indication if commit should be blocked' : 'Advisory feedback'}
    - Remediation steps`;
    
          const validation = await aiClient.call(validationPrompt, 'review', { 
            complexity: 'medium',
            maxTokens: 3000 
          });
          
          // Extract commit decision
          const criticalIssues = validation.toLowerCase().includes('❌ fail') || validation.toLowerCase().includes('critical');
          const commitStatus = block_on_issues && criticalIssues ? 'BLOCKED' : 'APPROVED';
          
          let result = `🛡️ **Pre-commit Guardian** (${language})
    
    **Status**: ${commitStatus === 'BLOCKED' ? '🚫 COMMIT BLOCKED' : '✅ COMMIT APPROVED'}
    **Checks**: ${checks.join(', ')}
    **Auto-fix**: ${auto_fix ? 'Enabled' : 'Disabled'}
    
    ${validation}`;
    
          // Generate Git hook integration if requested
          const gitHookPrompt = `Generate Git pre-commit hook integration:
    
    Validation Status: ${commitStatus}
    Issues Found: ${criticalIssues}
    
    Provide:
    1. **Git Hook Script** (bash/shell)
       - Pre-commit hook implementation
       - Integration with validation
       - Error handling and reporting
    
    2. **Installation Instructions**
       - How to install the hook
       - Configuration options
       - Troubleshooting guide
    
    3. **Workflow Integration**
       - CI/CD integration points
       - Team collaboration setup
       - Override procedures for emergencies`;
    
          const gitIntegration = await aiClient.call(gitHookPrompt, 'devops');
          
          result += `
    
    ---
    
    🔗 **Git Integration**
    
    ${gitIntegration}`;
    
          // Store validation results for metrics
          const validationData = {
            timestamp: new Date().toISOString(),
            language,
            status: commitStatus,
            checks: checks,
            critical_issues: criticalIssues,
            changes_size: changes.length
          };
          
          const storageData = await storage.read('validations');
          if (!storageData.validations) storageData.validations = [];
          storageData.validations.push(validationData);
          
          // Keep only last 500 validations
          if (storageData.validations.length > 500) {
            storageData.validations = storageData.validations.slice(-500);
          }
          
          await storage.write('validations', storageData);
          
          timer.end();
          return result;
        }
      },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'auto-fix suggestions' and 'Git integration' but doesn't specify whether fixes are applied automatically or suggested, what Git operations are performed (e.g., staging changes), error handling, or output format. For a validation tool with potential side effects, this leaves significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads key capabilities. Every word earns its place by highlighting advanced validation, auto-fix suggestions, and Git integration. However, it could be slightly more structured by separating core functionality from integration aspects.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter validation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what constitutes 'validation', what types of issues are detected, how results are returned, or what 'Git integration' entails. The agent lacks critical context about the tool's behavior and outputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema - it doesn't explain relationships between parameters (e.g., how 'auto_fix' interacts with 'block_on_issues') or provide usage examples. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose as 'Advanced pre-commit validation with auto-fix suggestions and Git integration', which includes specific verbs (validation, auto-fix) and resources (pre-commit, Git). It distinguishes from most siblings by focusing on pre-commit validation rather than analysis, chat, or generation. However, it doesn't explicitly differentiate from 'quality_guardian' which might have overlapping quality checking functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., Git repository context), when to choose it over 'quality_guardian' or 'codereview_expert', or specific scenarios where pre-commit validation is appropriate versus post-commit analysis tools. The agent must infer usage from the name and description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/emmron/gemini-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server