Skip to main content
Glama
232,168 tools. Last updated 2026-06-25 01:24

"namespace:io.github.nadine302324-commits" matching MCP tools:

  • Delete pending cr/* branches that will not be merged, such as those from failed operations or superseded drafts. This permanently removes the branch and its unmerged commits.
    MIT
  • Create a new Engineering Change Notice (ECN) for a project. Specifies ECN details like type, severity, and disposition, then commits to a branch or opens a pull request.
    Apache 2.0
  • Push local commits to a remote Git repository. Required: repo_path. Optional: remote, branch, force, set_upstream, dry_run. For staging, committing, and pushing in one step, use commit_and_push_changes.
    MIT
  • Organize code changes into well-structured commits with clear messages. Break large modifications into smaller, logical commits for better history.
    MIT
  • Visualize dependency graph evolution across git history. Analyze file counts, symbol counts, edge counts, and structural changes at sampled commits.
    Business Source 1.1

Matching MCP Servers

Matching MCP Connectors

  • Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.

  • GitHub MCP — wraps the GitHub public REST API (no auth required for public endpoints)

  • Retrieve commit history from a Bauplan branch with optional filters like date range, author, and message substring. Returns a list of commits with total count.
    MIT
  • Create an Engineering Change Order (ECO) that bundles specified ECNs, commits changes to a repository, and optionally generates a pull request.
    Apache 2.0
  • Scan a project folder to detect work done since last scan, including git commits, modified files, todo completions, and new documents. Updates scan summary and refreshes CLAUDE.md.
    AGPL 3.0
  • Sync GitHub repository data such as pull requests, issues, commits, and releases into Lore as searchable memories. Ingest tribal knowledge by connecting a GitHub repo to make organizational knowledge discoverable.
    MIT
  • Compare differences between Git branches or commits. Specify a repository path and target branch or commit to view line-by-line changes.
    MIT
  • Stage specific lines or ranges from Git changes for partial commits, enabling multiple logical commits from a single file with intermixed changes, including untracked files.
    MIT
  • Organize multiple Git changes into separate, focused commits using guided sessions with step-by-step instructions and change statistics.
    MIT
  • Compare two GitLab branches to see up to 30 commits and changed files. Useful for release note drafting and understanding differences between branches.
    MIT
  • Identify hidden coupling across modules by detecting cross-module co-change anomalies and shotgun surgery patterns in git commits.
    MIT