# Conventional Commit Linter MCP

> Conventional Commit Linter MCP for AI Agents allows you to validate commit messages against the Conventional Commits specification. It identifies breaking changes, checks structure, and calculates SemVer impact to keep your git workflow and changelogs changes predictable and automated. Perfect for maintaining a clean, standardized-lookingers Git history ander.

## Overview
- **Category:** automation
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_9gzHWUlBvxD1SI6JU2zSg1VSPENQmXMiFDSZ3WQq/mcp
- **Tags:** git, commit, semver, linter, conventional-commits

## Prompt Examples

**Prompt:** 
```
Check if this commit is valid: 'feat(ui): add button'
```

**Response:** 
```
The commit structure is valid with type 'feat' and scope 'ui'.
```

**Prompt:** 
```
Does 'fix: bug' contain a breaking change?
```

**Response:** 
```
No, no breaking change was detected in the message.
```

**Prompt:** 
```
What is the SemVer impact of 'feat: add user profile'?
```

**Response:** 
```
The impact level is minor.
```

## Capabilities

### Check commit structure and type
Ensures every commit follows the standard format for types like feat, fix, or chore.

### Identify breaking changes
Scans text for indicators of breaking changes to flag them for major version updates.

### Analyze SemVer impact
undefined

## Frequently Asked Questions

**How does the linter validate a commit?**
It analyzes the message structure using `verify_commit_structure` to check for type, scope, and description. Tools available: `your_tool_name`.

**Can it identify breaking changes?**
Yes, `analyze_breaking_change_presence` detects exclamation marks or BREAKING CHANGE footers.

**How is the version impact determined?**
The `classify_release_impact` tool calculates if the change requires a major, minor, or patch update.