No user-submitted related servers found.
Scored across 11 tools
Most tools have clearly distinct purposes: session control, checkpointing, repo listing, git history, map/code context, docs, and Lens each occupy a different workflow stage. The main possible confusion is between get_map and get_code_context, since both expose ShadowGit's dependency/symbol map, though their scopes differ and descriptions clarify when to use each.
The set is consistently snake_case and mostly follows a verb_noun pattern (get_docs, write_docs, start_session, end_session, list_repos). Minor deviations are git_command and checkpoint, which are action-oriented but not verb_noun in the same way.
Eleven tools is a well-scoped size for this domain, covering read paths, write paths, sessions, and repo discovery without obvious redundancy. Each tool appears to earn its place in the ShadowGit workflow.
The core lifecycle is covered: list projects, inspect history/map/code context/docs/Lens, start and end sessions, checkpoint, and write docs/Lens words. Minor gaps remain, such as no direct symbol/file search or explicit session-status tool beyond what list_repos and start_session imply.