gitrama-mcp

Analyzes staged git changes and generates semantically-correct conventional commit messages following the Conventional Commits specification (feat:, fix:, docs:, etc.). Integrates with git diff output to understand change scope and automatically categorizes commits by type, enabling consistent commit history that can be parsed by automated changelog and versioning tools.

Generates semantically meaningful git branch names based on commit intent, issue context, or feature descriptions. Follows common branch naming conventions (feature/, bugfix/, hotfix/, etc.) and can incorporate issue tracker IDs or ticket numbers. Integrates with the MCP protocol to receive context about planned work and output formatted branch names ready for immediate use.

Automatically generates comprehensive PR descriptions by analyzing the commits, branch name, and code changes between source and target branches. Structures descriptions with sections for summary, changes, testing notes, and breaking changes. Integrates with git metadata and MCP protocol to fetch branch diffs and produce markdown-formatted descriptions ready for GitHub, GitLab, or Bitbucket.

Maintains and manages contextual information about ongoing work streams, including related branches, commits, issues, and PR history. Stores work stream metadata via MCP protocol to provide consistent context across multiple git operations (commits, branches, PRs). Enables the system to generate more coherent messages and branch names by understanding the broader work context rather than treating each operation in isolation.

Provides MCP server implementation compatible with multiple editor environments including Cursor, Claude Desktop, Claude Code, Windsurf, and VS Code. Implements the Model Context Protocol specification to expose git workflow capabilities as standardized tools that editors can invoke. Handles MCP message serialization, tool registration, and context passing across different editor implementations.

Analyzes git diff output to extract semantic information about code changes, including files modified, change magnitude, affected functions/classes, and change type (addition, deletion, modification). Parses diff format to understand structural changes and provides this analysis as context for commit message, branch name, and PR description generation. Enables LLM-based generation to understand not just what changed, but why and how significant the change is.

Enforces and validates adherence to the Conventional Commits specification (https://www.conventionalcommits.org/) including proper formatting of commit type, scope, subject, and body. Generates commits that are parseable by automated tools for changelog generation, semantic versioning, and CI/CD pipelines. Supports optional configuration for custom commit types and scope validation.

Accepts issue/ticket IDs and context from external issue trackers (Jira, GitHub Issues, Linear, etc.) and incorporates this information into generated commits, branch names, and PR descriptions. Enables linking of git operations to external work tracking systems without manual copy-paste. Stores issue context within work stream metadata for consistent referencing across multiple git operations.

Analyzes code diffs to detect potential breaking changes (API signature changes, removed functions, database schema changes, dependency version bumps) and flags them for documentation in commit messages and PR descriptions. Uses heuristics and pattern matching to identify common breaking change patterns, then generates BREAKING CHANGE footer entries in conventional commit format. Can be configured to require explicit breaking change documentation before committing.