Skip to main content
Glama
680,450 tools. Updated 2026-10-20 09:17

"Guidance on Writing Git Commit Messages for Pushing to GitHub" matching MCP tools:

  • Scan git commit history to identify memory-worthy updates. Queue proposals for review without writing to active memory—use after meaningful commits or rescan entire history.
    MIT
  • Scan git repository history to detect exposed secrets in commit messages, author information, branches, and deleted files for security auditing.
    MIT
  • Display the commit history graph for a git repository. Opens an interactive UI for visual exploration of branches and commits.
    MIT
  • Read participation guidance and load contributions before writing, evidence for verification, direct API fallback protocol, or connection setup for Cairn tasks.
    MIT
  • Verifies that code-pattern memories remain relevant by comparing them with current git commit history, detecting staleness before acting on stored knowledge.
    MIT

Matching MCP Servers

  • A
    license
    B
    quality
    B
    maintenance
    Automatically generates conventional commit messages from staged git changes and checks repository status. Analyzes git diffs to create properly formatted commit messages following conventional commit standards.
    2
    24 PyPI
    9
    MIT
  • A
    license
    Not graded
    quality
    Not graded
    maintenance
    Analyzes git repository changes to generate conventional commit messages and summaries using OpenAI's GPT-4o-mini. It provides detailed tracking of modified, added, and deleted files to streamline the version control process.
    10 npm
    -

Matching MCP Connectors

  • Create or update multiple files in a single atomic GitHub commit with the Git Data API, avoiding SHA/ETag conflicts. Requires owner, repo, branch, commit message, and file array.
    -
    Destructive
  • Query Git commit history to understand changes, debug regressions, and find commit context. Search by keyword, file, or blame.
    MIT
  • Fix poorly written commit messages across a range by generating and applying improved versions, or preview them first with dry run.
    BSD 3-Clause
  • Automates Git commits by detecting changes, generating conventional commit messages, staging, committing, and optionally pushing to remote repositories while updating CHANGELOG.
    MIT
  • Publish any working directory as a GitHub repository. Automatically generates README and .gitignore, initializes git, creates the repo, commits, pushes, and returns the URL.
    MIT
  • Record an already-performed git commit against a gate session, marking it committed and updating the audit log. Use after a successful commit to complete the gate-controlled workflow.
    MIT
  • Validate git commit messages against project rules without AI or network access. Check type/scope format, subject style, forbidden footers, and more. Lint a literal message or a commit range, with optional deterministic scope suggestions.
    BSD 3-Clause
  • Execute Git commits with safety checks and user approval, requiring explicit confirmation to perform actual commits while supporting conventional commit messages.
    MIT
  • Aggregate git blame results by author for a file. Displays line counts, commit counts, and primary owner. Optionally scope analysis to a specific line range.
    MIT
  • Link a git commit SHA to a feature spec and optionally a task. Creates full traceability from code to commit to task to spec.
    MIT
  • Check for available updates to the Memory MCP server, querying GitHub Releases and git commits, and receive step-by-step update instructions when a new version is found.
    MIT
  • Generate ready-to-paste shell scripts for git post-commit hooks and CI steps. Install them to automatically send learning signals to your AI cognitive brain on every commit or build.
    Apache 2.0
  • Create a cryptographically signed Git commit envelope with Ed25519 provenance metadata, recording actor and tool for auditability.
    Apache 2.0
  • Identify the pull request that introduced a specific line in a file or a particular commit. Uses git blame and local merge commit data, with optional GitHub API fallback.
    MIT