Git is a distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
Why this server?
Provides a Git-backed knowledge graph and workflow: creates task branches, atomic task-scoped commits with trailers, attaches Git Notes under refs/notes/lognexus without changing commit SHAs, reconstructs branch timelines, and audits review-gate separation.
Why this server?
Integrates with Git status and diffs to audit modified files after edits, detect scope creep, and verify that physical changes match the approved plan.
Why this server?
Provides tools for working with hosted Git repositories in Adios workspaces, including branch creation and comparison, repository and branch listing, staging/unstaging, commits, pulls, pushes, Git status checks, and pull request workflows.
Why this server?
Allows importing existing Git repositories and exporting Kin repositories to Git, providing Git interoperability and version control history.
Why this server?
Enables deploying applications directly from a Git repository URL.
Why this server?
Scans git repositories and remote git URLs for malicious indicators without executing code, reporting findings with file:line evidence.
Why this server?
Provides Git repository tools for the CrossPad ecosystem, including repo status across all repos, committing staged changes, inspecting submodule drift, and updating submodules.
Why this server?
Respects .gitignore rules when scanning codebases, ensuring ignored files are excluded from context dumps
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).
