# Git Branch Naming Linter MCP for AI Agents MCP

> Git Branch Naming Linter MCP ensures your git branches follow specific patterns. It validates syntax, casing, and structural segments like ticket IDs to keep your repository clean and organized. Perfect for teams that need automated branch management and consistent development workflows in a DevOps-driven environment.

## Overview
- **Category:** automation
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_Nm5574h4YIAPOJyAMKRSPya8Zxk7PPgj0S6Tgobf/mcp
- **Tags:** git, linter, branching, workflow, devops

## Description

Keeping a repository clean is a constant battle in any busy development team. You've likely seen it happen: one developer actually follows the rules, but then someone pushes a'fix-it' or 'test-123' branch that breaks your entire naming convention. This MCP makes sure that doesn't happen by acting as a continuous linter for your git branches. Instead of manually checking every pull request, you can just ask your agent to audit the repo. You can even use Vinkius to manage all your development tools in one place. It handles everything from simple character checks to complex structural patterns, ensuring that every branch name is predictable and easy to read. This means no more guessing which branch belongs to a feature or which bugfix is tied to a specific ticket ID.

## Prompt Examples

**Prompt:** 
```
Is 'feature/PROJ-123-login' a valid branch name?
```

**Response:** 
```
Yes, the branch name **feature/PROJ-123-login** is valid. It follows the kebab-case convention and includes all required segments.
```

## Capabilities

### Enforce branch naming standards
Automatically checks if your git branches follow the rules you've set for your repository.

## Use Cases

### Cleaning up a messy repo
A developer asks their agent to audit all branches in the current repo. The agent uses the linter MCP to find every branch that doesn't match the pattern 'type/ID-description'.

## Benefits

- No more manual checking of branch names during code reviews.
- Enforces casing styles like kebab-case or snake_case automatically via check_branch_syntax.
- Ensures every branch contains the necessary ticket IDs using verify_structural_pattern.
- Reduces repository clutter and makes it'distributed search is easier with predictable branch names.
- capabilities_description_check_for_errors

## How It Works

The bottom line is you get a consistent, clean repository structure without manual oversight.

1. Connect your Git environment to the MCP via Vinkius.
2. Define your specific branch naming conventions, such as kebab-case or snake_case.
3. Run a check through your AI client to audit existing branches or new ones.

## Frequently Asked Questions

**What casing styles are supported?**
The linter supports kebab-case, snake_case, and camelCase. Tools available: `your_tool_name`.

**Can I validate Jira ticket IDs?**
Yes, by using the structural pattern verification tool with a custom regex.

**How does the batch audit work?**
You provide a list of branch names, and the tool returns a compliance rate and a summary of failures.