使用人工智能助手学习 Git 基础
在人工智能指导下提交、创建分支并推送代码。
使用人工智能助手学习 Git 基础 是 CoddyKit 上的免费 Vibe Coding 课时。 这是第 2 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Vibe Coding 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Vibe Coding 课程共包含 4 节课。
本课时的部分内容尚未翻译,以英文显示。
From Theory to Hands-On
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.
The Four Core Actions
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.
Starting a Project (init)
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:
I'm in my project folder in the VS Code terminal.
Walk me through starting Git tracking for this project, step by step.
I think the first command is `git init` -- confirm that, tell me
exactly what to type, and what I should see after each command.Staging vs Committing
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 changesgit commit -m "Add homepage"— save the snapshot
Think of staging as putting items in a box, and committing as sealing and labeling the box.
Your First Commit Prompt
Here's the exact prompt to make your first commit. Paste it into your AI assistant and follow along:
I just built my homepage and it works. I want to save this snapshot.
Give me the exact terminal commands to:
1. Stage all my changes
2. Commit them with the message "Add working homepage"
Then explain what each command did in one sentence.Seeing Your History
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:
const log = [
{ hash: 'a1b2c3', msg: 'Add working homepage' },
{ hash: 'd4e5f6', msg: 'Add navigation bar' },
{ hash: '7g8h9i', msg: 'Fix mobile layout' }
];
console.log('Project history (newest last):');
log.forEach(c => console.log(' ' + c.hash + ' ' + c.msg));
console.log('\nEach hash is an ID you can return to.');Branching to Experiment
Want to try a redesign without risking your working app? Make a branch.
git branch new-design— create the branchgit 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.)
Merging Back In
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:
I created a branch called `new-design`, tested it, and it works great.
Give me the exact commands to:
1. Switch back to my main branch
2. Merge `new-design` into it
If there's a merge conflict, tell me how to spot it and what to do.Connecting to GitHub (push)
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.
The .gitignore File
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:
Create a .gitignore file for a beginner web project.
Make sure it ignores node_modules, .env files with secrets,
and any OS junk files like .DS_Store. Explain why each
entry should be ignored, briefly.Your Repeatable Workflow
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.
Quick Check
Let's check your grasp of the core Git flow.
Recap & What's Next
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.
用 AI 导师学习 JavaScript — 免费
在浏览器中编写并运行真实代码,获得全天候 AI 导师的即时帮助,并在网页或应用中继续学习。
- 课程
- 25
- 课程
- 100
常见问题解答
「使用人工智能助手学习 Git 基础」课时是免费的吗?
是的 — 「使用人工智能助手学习 Git 基础」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Vibe Coding 课程的其余内容,请升级到 CoddyKit PRO。 Vibe Coding 课程共包含 4 节课。
「使用人工智能助手学习 Git 基础」这节课中我会学到什么?
在人工智能指导下提交、创建分支并推送代码。 你通过在浏览器中直接运行的动手代码来练习 Vibe Coding,全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Vibe Coding 需要有经验吗?
无需任何先前经验。CoddyKit 上的 Vibe Coding 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 2 节课,共 4 节。
「使用人工智能助手学习 Git 基础」课时需要多长时间?
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。
我能在这节 Vibe Coding 课中编写并运行代码吗?
能。每节 Vibe Coding 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。
此课程中的所有课时
- 版本控制为何重要
- 使用人工智能助手学习 Git 基础
- 让人工智能编写提交消息
- 安全撤销错误