0Pricing
Vibe Coding · 강의

인공지능 도우미와 함께하는 Git 기초

인공지능의 안내에 따라 커밋하고 브랜치를 만들며 푸시하십시오.

인공지능 도우미와 함께하는 Git 기초은(는) CoddyKit의 무료 Vibe Coding 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 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 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.

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 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.)

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.

자주 묻는 질문

“인공지능 도우미와 함께하는 Git 기초” 강의는 무료인가요?

네 — “인공지능 도우미와 함께하는 Git 기초” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Vibe Coding 강의 전체를 잠금 해제할 수 있습니다. Vibe Coding 강의에는 총 4개의 강의가 포함되어 있습니다.

“인공지능 도우미와 함께하는 Git 기초”에서 뭘 배우나요?

인공지능의 안내에 따라 커밋하고 브랜치를 만들며 푸시하십시오. 브라우저에서 직접 실행하는 실습 코드로 Vibe Coding을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Vibe Coding을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Vibe Coding은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 2번째 강의입니다.

“인공지능 도우미와 함께하는 Git 기초” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Vibe Coding 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Vibe Coding 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

  1. 버전 관리가 중요한 이유
  2. 인공지능 도우미와 함께하는 Git 기초
  3. 인공지능에게 커밋 메시지 작성 맡기기
  4. 안전하게 실수 되돌리기
← Vibe Coding(으)로 돌아가기