Validate commit message, branch, author, and push safety of a local git repository in one read-only call. Ensure repository state meets your standards before commits or deployments.
MIT
465,637 tools. Updated 2026-08-19 05:43
"Guidance on Writing Git Commit Messages for Pushing to GitHub" matching MCP tools:
- Deploy a static or Next.js site by committing and pushing to Vercel's pipeline. Wraps git operations with governance and auto-injects ChatOps env vars.MIT
- Check character limits for each metadata field and soft guidance for screenshot headlines and captions before writing copy.MIT
- Apply multi-file changes on an isolated git branch, auto-commit and fast-forward merge, with optional verification and rollback on failure.MIT
- Provide typical callees, familiar imports, and replacement guidance for a file based on repository patterns to inform code writing.MIT
- Scan git repository history to detect exposed secrets in commit messages, author information, branches, and deleted files for security auditing.MIT
Matching MCP Servers
- AlicenseAqualityCmaintenanceAutomatically 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.28MIT
- Alicense-quality-maintenanceAnalyzes 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.5
Matching MCP Connectors
GitHub MCP — wraps the GitHub public REST API (no auth required for public endpoints)
Manage repositories, users, releases, and automate GitHub workflows
- Display the commit history graph for a git repository. Opens an interactive UI for visual exploration of branches and commits.MIT
- List git commits linked to a session ID, returning link evidence and metadata. Detect and quarantine unsafe summaries without guessing commit intent.MIT
- Verifies that code-pattern memories remain relevant by comparing them with current git commit history, detecting staleness before acting on stored knowledge.MIT
- View changes staged for commit in a Git repository to review modifications before finalizing the commit.MIT
- Deterministically validate commit messages against guidelines—no AI, network, or credentials needed. Lint a single message or a commit range, enforcing format, style, and footer rules with a YAML pass/fail report.BSD 3-Clause
- Query Git commit history to understand changes, debug regressions, and find commit context. Search by keyword, file, or blame.MIT
- Rewrites commit messages in a range with AI improvements, applying by default or previewing with dry_run. Protects against rewriting published history.BSD 3-Clause
- Track a single function's complexity over time using git history, with per-commit snapshots of cyclomatic complexity, nesting, params, and lines.MIT
- Execute a git commit after the user reviews and approves the generated commit message.MIT
- 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
- Commit staged changes in a CrossPad repo with alias resolution and merge conflict protection. Optionally stage specific files before committing.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