Git is a distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
Why this server?
Allows pushing knowledge base changes to a remote Git repository via the commit_backup tool.
Why this server?
Integrates with Git repositories by providing a pre-commit hook definition that enforces the Governed Agent fail-closed verification gate before commits are accepted.
Why this server?
Uses Git to check stored memories against the working tree and commit history, providing staleness verdicts and detecting path/commit drift so outdated facts are flagged rather than trusted.
Why this server?
Provides structured access to local Git repositories, enabling operations such as checking repository status, viewing filtered commit logs, generating unified diffs for working trees or between refs, running file blame with line ranges, listing and managing branches with tracking info, and handling stashes (list, push, pop, apply).
Why this server?
Source code version control and development workflow management.
Why this server?
Analyzes Git-tracked repositories, using git history to rank functions by churn and change coupling, and providing a commit gate that blocks changes that add complexity debt.
Why this server?
Provides tools for cloning Git repositories as part of deployment workflows.
Why this server?
Provides shared team memory synchronized through private Git repositories, letting users create or join shared spaces and exchange notes with teammates via git push/pull.
Why this server?
Enables cloning and working with the source code repository for development purposes.
