Context

Git tools are listed alongside file system tools (#18) as M3 scope in the DESIGN_SPEC. Agents need git operations to work on codebases — clone repos, create branches, commit changes, view diffs, etc.

Acceptance Criteria

• git_clone tool: clone a repository into the agent workspace
• git_commit tool: stage and commit changes with a message
• git_diff tool: show changes (staged, unstaged, between branches)
• git_branch tool: create, switch, list branches
• git_status tool: show working tree status
• git_log tool: show commit history with optional filtering
• All tools implement the tool interface from Design and implement basic tool system (registry, invocation, results) #15
• All tools execute through the subprocess sandbox
• Workspace boundary enforcement (agents can only operate in their assigned workspace)
• Comprehensive error handling (not a git repo, merge conflicts, network errors, etc.)
• Unit tests with temporary git repositories for all operations
• Edge case tests: empty repos, detached HEAD, merge conflicts

Dependencies

• Design and implement basic tool system (registry, invocation, results) #15 — Tool system (done)
• Subprocess sandbox issue (tools must execute through sandbox)

Design Spec Reference

• §11.1 — Built-in Tools (Git Tools category)
• §15.3 — tools/git_tools.py