GenPark Git Commit Conventional Semantic Linter
LocalAbout GenPark Git Commit Conventional Semantic Linter
A Python library and MCP server for linting Conventional Commits 1.0.0 messages and grouping entries for changelogs. It parses breaking changes and issue references for projects that need consistent commit checks and changelog organization.
Key features
- 01Conventional Commits 1.0.0 linting
- 02Breaking-change parsing
- 03Issue-reference parsing
- 04Changelog grouping
- 05Python standard library only
Use cases
- 01Checking commit messages against Conventional Commits
- 02Grouping commits for changelog preparation
MCP support
Runs as an MCP server via `python mcp_server.py`, exposing its commit-linting and changelog functions to MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEGenPark Git Commit Conventional Semantic Linter
Conventional Commits 1.0.0 semantic linter and changelog grouping engine parsing breaking changes and issue refs.
Part of the GenPark AI Agent Skills Ecosystem.
🌟 Key Features
- 100% Python Standard Library: Zero third-party runtime dependencies.
- MCP Native: Plugs directly into Claude Desktop, Cursor, LobeChat, and autonomous agent DAGs.
- Production Resilience: Strict schema conformance, zero data loss, enterprise hardened.
🚀 Installation & Usage
Run as an MCP server:
python mcp_server.py
Use directly as a library:
from client import *
See example_usage.py for comprehensive integration demonstrations.
📄 License
MIT License. Maintained by GenPark AI.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.