พื้นฐาน Git พร้อมผู้ช่วยปัญญาประดิษฐ์

Last lesson you learned why version control matters. Now you'll actually use it — and you won't memorize a single command.

Your AI assistant (Cursor, Claude Code, Copilot, or even ChatGPT) will write every Git command for you. Your job is to understand what each step does so you stay in control.

By the end, you'll have made a commit, a branch, and a push. Let's go.

99% of Git work is just four actions:

• init — start tracking a project (once per project)
• commit — save a snapshot
• branch — make a parallel copy to experiment
• push — upload your snapshots to GitHub

Learn these four and you can build real apps. Everything else you can ask AI for as you need it.

To begin tracking a folder, you run git init once. Most tools (Cursor, Replit, GitHub Desktop) do this with a button, but here's what it looks like.

Don't type this blindly — paste it into your AI and ask it to confirm. Here's a prompt to do that:

One thing that confuses beginners: before you commit, you stage your changes. Staging means "these are the changes I want in this snapshot."

Two-step rhythm: stage what you want, then commit it with a message.

• git add . — stage all your changes
• git commit -m "Add homepage" — save the snapshot

Think of staging as putting items in a box, and committing as sealing and labeling the box.

Here's the exact prompt to make your first commit. Paste it into your AI assistant and follow along:

After a few commits, you'll want to see your history. The command is git log. Tools show it as a clickable timeline.

Here's a tiny simulation of what your history feels like — a list of save points with messages:

Want to try a redesign without risking your working app? Make a branch.

• git branch new-design — create the branch
• git checkout new-design — switch to it

Now you're working in a parallel copy. Your main version is frozen and safe. Build wild ideas here.

Modern shortcut: git checkout -b new-design creates and switches in one step. (Your AI knows all these.)

When your experiment works, you bring it into your main version with a merge.

You switch back to your main branch and merge the experiment in. If something conflicts, AI is excellent at resolving it. Here's a prompt for the whole flow:

Push uploads your commits to GitHub so they're backed up online and shareable.

The easiest path: in Cursor or VS Code, click "Publish to GitHub." It creates the online repo and pushes for you.

If you prefer the terminal, your AI will give you the git remote add and git push commands. Once connected, future pushes are a single click or git push.

Some files should NOT be saved to Git — like secret API keys or huge auto-generated folders (node_modules).

A .gitignore file lists what Git should skip. This keeps your repo clean and your secrets safe.

Don't hand-write it — ask AI. A solid prompt:

Here's the loop you'll use every single day as a vibe coder:

• Build a small feature with AI
• Test it — does it work?
• Stage and commit with a clear message
• For risky ideas, work on a branch first
• Push to GitHub to back everything up

Repeat. This rhythm keeps your project safe, organized, and always recoverable — no memorization required.

Let's check your grasp of the core Git flow.

You can now run the full Git basics — with AI writing the commands:

• init starts tracking a project (once)
• stage + commit saves a snapshot with a message
• branch lets you experiment safely, merge brings it back
• push backs everything up on GitHub
• .gitignore keeps secrets and junk out

Next lesson: Letting AI Write Commit Messages — get a clean, professional history with almost no effort.