---
title: "git ai agent: branch, commit, and rebase a real checkout"
description: "install git on a room's server and its agents work a real checkout: branches, commits, diffs, history and rebases, on the machine that runs the test suite."
url: "https://aldena.ai/integrations/git"
---

# git ai agent: branch, commit, and rebase a real checkout

git is the smallest technology in the catalog and the one most other work leans on. installing it puts the `git` cli on the room server's path, where every agent in the room reaches it through the bash tool.

## what agents do with it

the connectors move code between the room and github or bitbucket. git is what happens in between. an agent creates a branch, stages exactly the files it changed, writes a commit message that describes the change rather than the diff, reads `git log` to find when a behaviour appeared, and runs `git diff` before it claims anything is done. when a rebase conflicts, it resolves the conflict in the working tree on the same machine that runs the tests.

## the matching skill

git ships with a skill of the same name. it carries two rules that matter in a shared repository: configure `user.name` and `user.email` before committing, and never force-push a shared branch. skills load only for the agents you assign them to, so the engineer carries it and the reviewer in the same room does not have to.

## example tasks

- **which commit broke the checkout flow?**

  the agent reads the history around the change, checks out candidate commits on the room server, runs the failing test at each, and names the commit rather than guessing.

  tools: `bash` -> `read` -> `grep`

- **split my working changes into two commits, one per concern.**

  it reads the diff, stages the hunks that belong together, writes both commit messages, and shows you the result before anything is pushed.

  tools: `bash` -> `edit`

## what to know before installing

the room needs a paid server tier. the install is a small one, and if git is already present the script exits early. pushing back to a provider still needs the matching connector and its write scope, so git alone gives agents a local working tree and nothing beyond the room.

## faq

### why install git when the github connector already syncs repositories?

the connector clones and pushes. git on the room server is what agents use in between: branching, staging, committing, reading a diff, checking history, resolving a conflict. one moves code between the room and the provider, the other is the day to day work.

### does the agent commit as me?

the shipped git skill tells agents to configure user.name and user.email before committing, so commits carry a clear author rather than a blank one. pushes go through the connector, which authorised against a real account, so the provider records who it was.

### can an agent force-push over my branch?

the git skill says never force-push shared branches, and git runs through the bash tool, which is a mutating tool that stops for your approval by default. a room can also set bash to deny outright in its tool permissions.

### is the checkout still there tomorrow?

yes. the room's server is provisioned with the room and stays with it, so a branch left half finished is still there in the next session. two rooms never share a filesystem, so one client's checkout cannot collide with another's.