Git Branch Naming Linter

Git Branch Naming Linter MCP Connector for Claude

B

Validates git branch names against specific naming conventions and structural patterns.

0 tools Official Updated Oct 1, 2026 Official Vinkius Partner

This MCP server provides tools to ensure repository cleanliness by enforcing branch naming standards. You can use check_branch_syntax to verify character integrity, casing styles like kebab-case or snake_case, and maximum length constraints. The verify_structural_pattern tool checks for required segments like type and ticket ID, while audit_branch_batch allows you to analyze multiple branches at once to identify non-compliant names in your workflow.

Available Tools

your_tool_name

gitlinterbranchingworkflowdevops

0 tools expose this connector's capabilities to your AI agent.

See how to talk to your AI agent using Git Branch Naming Linter.

Check if 'feature/PROJ-123-login' is valid for kebab-case.

The branch name 'feature/PROJ-123-login' is valid and follows the kebab-case convention.

Is 'bugfix_task-456' a valid snake_case branch?

No, 'bugfix_task-456' is invalid because it contains a hyphen, which is not allowed in snake_case.

Audit these branches: ['feat/JIRA-1', 'hotfix/fix-it'] using segments type, id, description.

The audit found 0% compliance. The branch 'feat/JIRA-1' is missing the description segment.

The linter supports kebab-case, snake_case, and camelCase. Tools available: `your_tool_name`.

Related Connectors