DocsAdvanced

Git Integration

Inspect, diff, and commit the AI's changes from inside KingCoding.

What Git Integration Does

If your project is a git repo, KingCoding tracks changes and surfaces them in the UI so you can review before committing.

  • See the current branch and staged / unstaged changes
  • Review per-file diffs
  • Write a message and commit in place
  • Leave the message empty to let AI generate it from the diff

Reviewing Changes

A status badge sits in the project header / sidebar. Open it to list changed files, then click one to view the diff.

Committing

  • Stage the changes you want (or stage everything)
  • Write the commit message
  • Click Commit

Auto-commit on Task Completion

When the commit message is empty, KingCoding can generate one from the current diff. Adding a Gemini API key under Settings → General makes that path faster.

Branch Workflow

  • The current branch name is shown in the header
  • Ask the AI to "work on a new branch" and it'll cut one before editing
  • Destructive ops (rebase, hard reset) need explicit instructions; the AI avoids them by default

Practical Use

  • Cut a branch before any meaningful AI work
  • One task = one branch = one PR keeps reverts cheap
  • Always eyeball the diff before committing — strip stray edits early
← PreviousPreviewNext →Memos