Git 106: ใช้ Git กับ AI agent อย่างปลอดภัยGit 106: use Git safely with AI agents

Git becomes more important when AI can edit files for you.

The goal is not to block AI. The goal is to make every change inspectable.

Start clean

Before asking an AI agent to edit a project:

git status

If the tree is dirty, decide what the changes are.

• Commit work that is ready.
• Move unrelated work away.
• Tell the agent which files are already changed and must not be overwritten.

Do not let an AI task start from a confusing state.

Create a scoped branch

Use a branch per task:

git switch -c fix-workshop-copy

The branch name should explain the job.

Bad:

ai-stuff

Better:

docs-git-10x-lessons

Give the agent file boundaries

A strong AI instruction includes ownership:

Edit only:
- src/content/workshops/git-10x/*.mdx
- src/lib/catalog.ts

Do not edit:
- src/styles/globals.css
- database schema
- unrelated workshop content

Before finalizing, summarize changed files and tests run.

This works because Git can later verify whether the boundary was respected.

Review the diff, not the vibe

After the agent finishes:

git status
git diff

If you already staged changes:

git diff --staged

Look for:

• unrelated files
• deleted content
• changed URLs or slugs
• secrets
• claims that need sources
• tests that should be updated

Do not commit until the diff makes sense.

Commit in meaningful chunks

If one AI run changed many things, split commits by purpose.

Example:

docs: add Git 10x lessons
catalog: register Git 10x workshop
docs: update free workshop central plan

Small commits make review and rollback easier.

Basic recovery habits

Use recovery commands carefully.

Helpful read-only checks:

git status
git log --oneline -10
git diff

Common recovery ideas:

• If a file is not staged and you do not want the change, restore that file.
• If changes are staged but not committed, unstage before deciding.
• If a commit is wrong but already shared, prefer a new corrective commit or git revert instead of rewriting shared history.

When in doubt, stop and ask. Many Git mistakes become worse when you panic-run commands.

Final AI + Git workflow

Use this as your default loop:

1. git status
2. create or choose a task branch
3. tell AI the goal and file boundaries
4. let AI edit
5. git status
6. git diff
7. run tests or checks
8. git add specific files
9. git diff --staged
10. git commit with a clear message
11. push and open review if needed

The point is not ceremony. The point is control.

Git 10x final checklist

• You know Git is local version control, not GitHub.
• You can create a repository and read status.
• You can inspect diffs before staging.
• You can make meaningful commits.
• You can use branches for isolated work.
• You understand remotes, pull, push, and where GitHub fits.
• You can use Git as a safety rail for AI-assisted edits.

References

• Pro Git: About Version Control
• Pro Git: Getting a Git Repository
• Pro Git: Recording Changes to the Repository
• Pro Git: Viewing the Commit History
• Pro Git: Basic Branching and Merging
• Pro Git: Working with Remotes
• Git reference: git-status
• Git reference: git-push
• GitHub Docs: About pull requests