Skip to main content
Glama
620,466 tools. Updated 2026-09-29 00:53

"pre-commit" matching MCP tools:

  • Detect CI/CD configuration files (GitHub Actions, GitLab CI, Jenkins, CircleCI, Docker, pre-commit) to evaluate production readiness.
    MIT
  • Configure Husky git hooks to validate commit messages and run pre-commit checks, optionally integrating lint-staged.
    MIT
  • Validate commit message, branch name, and author details together in one call, returning pass/fail/warn results with fixes and suggestions before you commit.
    MIT
  • Validate a commit message against commit-check rules (Conventional Commits, subject length, body, sign-off). Get pass/fail status with warnings and fixes before committing.
    MIT
  • Retrieve commit details by commit ID or hash. Get hash, message, author, date, tags, and associated builds with status and artifacts.
    MIT
  • Return the merged validation rules for a repository, including enabled checks and patterns, to learn expected commit message and branch name formats or diagnose validation failures.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Query React commit data by component, time range, or index to investigate render performance. View cascade trees to trace which parent triggered each commit.
    Apache 2.0
  • Resolve a branch, tag, or commit to a concrete commit SHA before deploying, so deployments are authorized for that exact commit, not for whatever the branch points to later.
    MIT
  • Validate and commit a batch of graph mutations atomically in one call, managing transaction begin, validation, and commit so code changes apply consistently.
    Apache 2.0
    Destructive
  • Commit staged index content to a Git repository with branch and head validation, ensuring idempotent and hook-checked commits.
    MIT
  • Query Git commit history to understand changes, debug regressions, and find commit context. Search by keyword, file, or blame.
    MIT
  • Create a commit with a message or amend the last commit, optionally skipping pre-commit hooks. Use after staging changes to record them, or to fix the previous commit.
    MIT
  • Automates Git commits by detecting changes, generating conventional commit messages, staging, committing, and optionally pushing to remote repositories while updating CHANGELOG.
    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
  • Execute Git commits with safety checks and user approval, requiring explicit confirmation to perform actual commits while supporting conventional commit messages.
    MIT
  • Start a transaction to batch multiple model changes together, applying them all at once upon commit or discarding on rollback.
    Cryptographic Autonomy 1.0 (Combined Work Exception)
  • Scan staged changes for secrets and run code review in parallel before commit. Block the commit if any secret is found; otherwise return a pass, warn, or blocked verdict.
    MIT
  • Release a pre-commit hold to return unspent reservation to the budget. Use for planned payments cancelled before settlement.
    Apache 2.0